On Mon, Jan 24, 2011 at 7:30 PM, James Oisin Flynn <[email protected]> wrote: > Thank you. I had seen this as an option, though it does, as you point out, > necessitate having the client listening... That can pose a bit of a problem. > If I can get away with that, I'll try it, otherwise I guess I'll just play > with timeouts.
For async stuff ... I used to do it the axis2 way, but found that just starting a thread on the service side and returning immediately works for what I need it to do. I mean if you need a client listening anyways, what's the point? There might be a point in some spec but starting a thread is trivially easy. Last time I looked at the async code generation it starts a thread anyways, IIRC. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
