Matthew Toseland wrote: > Well, in the current API, you can either come up with a unique name, or not > have any client-name-specific state i.e. either have no persistent requests > or store them all on the global queue. I don't see how any other solution > would help - if you start persistent requests, exit, another client steals > your name, you give way to that client, then you'll have lost them. > >
...or another client may flood mine with leftover requests. Very unlikely case, but no magic either if some future version of the protocol would equip clients to handle their own persistence. Thanks for listening, Juergen
