Re: [soaplite] question on sending a simple message versus waiting for a result
- Hi, Joe!
> object to a method, and simply have the call return right awayAs Duncan already pointed it depends on transport protocols. HTTP is
> without waiting for the method to return a result.
request/response protocol by nature, so you need to return something.
It might be 202 ACCEPTED or 204 NO CONTENT code, but something must
be returned, otherwise client won't be able to distinguish between
broken connection and legitimate lack of response. To do that, you
may override make_response method on server side that which returns
HTTP::Response object and put any information you need there. You
will need to check status on client side
($soap->transport->is_success will return true when 2xx status code
Let me know if you still have a questions or need examples on how to
Best wishes, Paul.
--- J Landman <landman@...> wrote:
> I am using SOAP::Lite for a project, and it is wonderful. Of__________________________________________________
> course, I
> ran into something that I hoped would not be hard to solve. What I
> to do is quite simple to state. I want to (within SOAP::Lite) send
> object to a method, and simply have the call return right away
> waiting for the method to return a result. That is, the method has
> desireable side effects, and no real return information.
> Currently I have to look at either polling a queue that the method
> an entry into, or forking a process. I want something more like
> "fire and
> forget", or basic messaging. Can this be done easily within
> Suppose we had a method named return_immediately rather than
> result, so
> that our calls might look like
> Clues/hints welcome. Thanks!
> Joe Landman,
> ------------------------ Yahoo! Groups Sponsor
> To unsubscribe from this group, send an email to:
> Your use of Yahoo! Groups is subject to
Terrorist Attacks on U.S. - How can you help?
Donate cash, emergency relief information