Ralph Meijer a écrit :
On Mon, Aug 29, 2005 at 08:21:39PM +0200, Norman Rasmussen wrote:
I think the point here, is that nothing stops you from writing an
AdHoc command that returns a list of currently executing commands, and
allows you to pick on, and cancel it.
Sure, you could use JEP-0050 for that, but that wasn't the complete
problem of the other Ralph. He wanted to be able to cancel a placed
request *and* still receive results asynchronously. Or do you propose
not replying to the original <iq/> until the request has indeed been
completed or cancelled?
Wouldn't it be possible to go like this (oversimplified not valid but
should get the point) :
client: <iq id='cmd1' ...>do-something-for-me</iq>
server: <iq id='cmd1' type='result' ...>ack #foo</iq> (means: ok, I'll
do it for you, I number it #foo)
Then later, either:
client: <iq id='cmd2' ...>cancel #foo</iq> (means: I change my mind,
stop it)
server: <iq id='cmd2' type='result' .../> (means: ok, task cancelled)
Or:
server: <iq id='res1' ...> #foo gave result bar</iq> (means: here is the
answer to what you asked and I call #foo)
client: <iq id='res1' type='result' .../> (means: got it, thanks!)
That way you have both asynchronous results and the ability to cancel
something after some time. You could even imagine doing more than
cancelling: changing the request.
My two eurocents,
Snark on #gnomemeeting
_______________________________________________
jdev mailing list
[email protected]
http://mail.jabber.org/mailman/listinfo/jdev
