RE: [wsdm] Groups - Request State Model Choices for WSDM.doc uploaded

["Murray, Bryan P." <bryan.murray@hp.com>]

I think what is bothering me about the request state models is that we
are trying to combine the request processing system of a web service
with the execution of a single request. Also we have mixed the "states"
such that some of them represent a point in time and others represent an
ongoing activity.

A request processing system (part of a web service) might have states
such as: waiting for request, deserializing message,
authenticating/authorizing sender, dispatching to business logic. I
would expect that the transition from one state to the next might
produce a notification. Some request processing systems will execute
requests in-line one by one so their states could be included here.
Other request processing systems will parallelize the execution of
several requests at once and individual request process would not make
sense here.

The states involved in a single request become a little more difficult
to define precisely because different request processing systems might
be less capable and thus the request itself will need to handle some of
the tasks that might otherwise have been handled by the app-server. If
we assume support from an app-server, all requests will have a state for
executing business logic. Transitions to that state would be request
received. Transitions out of that state would be business processing
complete. But these would not be states of themselves - they are just
transitions. Some requests might have additional states for generating
response, serializing response, sending response and a similar set for
failures. Transitions between these might produce notifications. Not all
requests will result in either a response or a fault message being sent
(one-way messages) so the state model needs to allow for bypassing these
states.

I have assumed that notifications are sent on transitions from one state
to another and have tried to name states as if they take some time and
are not an instant in time.

I am not sure whether we are trying to model the request processing
system or just a request. Maybe we can combine them somehow. Whatever is
done we need to allow for one-way messages in our model.

Bryan

-----Original Message-----
From: Igor.Sedukhin@ca.com [mailto:Igor.Sedukhin@ca.com] 
Sent: Thursday, August 05, 2004 4:50 PM
To: wsdm@lists.oasis-open.org
Subject: [wsdm] Groups - Request State Model Choices for WSDM.doc
uploaded

The document Request State Model Choices for WSDM.doc has been submitted
by Igor Sedukhin (Igor.Sedukhin@ca.com) to the OASIS Web Services
Distributed Management TC document repository.

Document Description:


Download Document:  
http://www.oasis-open.org/apps/org/workgroup/wsdm/download.php/8491/Requ
est%20State%20Model%20Choices%20for%20WSDM.doc

View Document Details:
http://www.oasis-open.org/apps/org/workgroup/wsdm/document.php?document_
id=8491


PLEASE NOTE:  If the above links do not work for you, your email
application may be breaking the link into two pieces.  You may be able
to copy and paste the entire link address into the address field of your
web browser.



To unsubscribe from this mailing list (and be removed from the roster of
the OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/wsdm/members/leave_workgrou
p.php.