anonymous wrote : 2. Gateway sync="false": Gateway will async invoke service and
return an empty response payload in the http response.
I think the section in the HTTP spec regarding a 202 status code gives some guidance on
how this might work:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.2.3
In that section it says
anonymous wrote : The entity returned with this response SHOULD include an indication of
the request's current status and either a pointer to a status monitor or some estimate
of when the user can expect the request to be fulfilled.
One use case for the sync="false" is to kick off a long-running process and the
202 status can be used to indicate that the request was received and the accompanying
response payload can be used to give the client some information about when the job might
be done, a URL to retrieve the status, etc. This is partially supported in the JBR gateway
with the asyncResponse property.
Can support for that type of interaction be included?
Thanks,
Scott
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252601#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...