RE: Issue: Synch/Asynch Web services

Well, it's not something that I have thought through very clearly.  It
just seems to me that if I were a potential user of a Web service that
performed the X function, and if I wanted to do the X function
synchronously (that is, waiting for the answer to come back) -- well, I
might like to have some idea that a Web service could perform the X
function in some time that I would be willing to wait.  How long I am
willing to wait is kind of up to me.  Some people have shorter attention
spans than others.  So it seems to me that it might not be so hot if a
Web service advertised, somehow, "I am available for synchronous
access".  Well, is that synchronous access for someone willing to wait
an hour, or for someone with an attention span like mine?  So it seems
to me that it would be better if a Web service were able to advertise,
"This is the response time I have typically given in the past.  If that
meets your needs, go for it ..."
 
-----Original Message-----
From: ECKERT,ZULAH (HP-Cupertino,ex1) [mailto:zulah_eckert@hp.com] 
Sent: Wednesday, August 06, 2003 6:31 PM
To: Cutler, Roger (RogerCutler); www-ws-arch@w3.org
Cc: www-wsa-comments@w3.org
Subject: RE: Issue: Synch/Asynch Web services


 
Hi Roger,
 
   Access to past performance metrics, etc. will be dealt with with
logging. I'm not sure how this relates to asynchronous messaging - can
you clarify the question below.
 
 
>  -Could/should a management interface expose information to potential
users of a WS about past performance metrics and/or expectations of  
>  relevance to the issue of s/sa usage?  (e.g. expected/observed
response times)? 
 
The major application of asynchronous messaging is for events that are
sent between a resource and a manager.
 
Zulah