W3C home > Mailing lists > Public > www-ws-arch@w3.org > February 2003

Re: Snapshot of Web Services Glossary

From: Walden Mathews <waldenm@optonline.net>
Date: Tue, 25 Feb 2003 10:26:41 -0500
To: Assaf Arkin <arkin@intalio.com>, www-ws-arch@w3.org
Message-id: <000801c2dce2$4d022120$1702a8c0@WorkGroup>

> > What do you think about, simply:
> >
> > Synchronous operations may fail by "timing out" i.e., taking too long.
> > For asynchronous operations, "timing out" is undefined.
> This is probably correct, but I think it defines the symptom rather than
> cause.

The way I'd put that is that it's more of a *designation* of the concept,
rather than a *definition*.  (These are terms used by Michael Jackson in
his text on software requirements and specifications.)

But perhaps designation is more appropriate for the case at hand,
since definitions tend to be beyond the reach of the general readership.
If there are no other objections, I'd like to propose that the simple
language above be adopted.

Are there uses of 'synchronous' and 'asynchronous' for which the above
is not expressive enough, anyone?  Can those cases perhaps be
covered using other terms, such as "blocking", "solicited", etc?

Received on Tuesday, 25 February 2003 10:31:38 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:41:03 UTC