<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
I did not give it much thought, and did not look into how it would look
as resource properties. My service does expose some resource
properties, but I found them to be harder to configure, and in my
current way of handling them, I would have had to retrieve each
resource property in a separate WS call, being very inefficient :(
Maybe I could have made an encapsulating object that held all the
system metrics, similar to what my function does, but ah well... in the
next version...<br>
<br>
Ioan<br>
<br>
Ben Clifford wrote:
<blockquote
cite="mid:Pine.LNX.4.64.0705231827580.22628@dildano.hawaga.org.uk"
type="cite">
<pre wrap="">On Wed, 23 May 2007, Ioan Raicu wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I found it simpler to simply add a monitorStatus function that returned
a bunch of system metrics!
</pre>
</blockquote>
<pre wrap=""><!---->
A damnation of the GT WS Resource Properties implementation!
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
============================================
Ioan Raicu
Ph.D. Student
============================================
Distributed Systems Laboratory
Computer Science Department
University of Chicago
1100 E. 58th Street, Ryerson Hall
Chicago, IL 60637
============================================
Email: <a class="moz-txt-link-abbreviated" href="mailto:iraicu@cs.uchicago.edu">iraicu@cs.uchicago.edu</a>
Web: <a class="moz-txt-link-freetext" href="http://www.cs.uchicago.edu/~iraicu">http://www.cs.uchicago.edu/~iraicu</a>
<a class="moz-txt-link-freetext" href="http://dsl.cs.uchicago.edu/">http://dsl.cs.uchicago.edu/</a>
============================================
============================================
</pre>
</body>
</html>