On Wed March 18 2009 7:10:46 am fmireaux wrote: > Thanks, > > But it seems to me that, in some cases, it's not a matter of configuration > : a client program could want to indicate that a request is the last one of > a series, letting RM interceptors do what they have to do with this > information (beginning by using the lastmessage protocol header for the > request as they do when max sequence length is reached).
Ran into the same issue with WS-SecureConversation. I needed a way for the application to let the sec-conv runtime know to cancel the conversation token. I ended up just adding a property that could be set on the request context to let the runtime know to cancel it after the next request. Something similar could be done for WSRM. It's not ideal as you need to know ahead of time that the next request really is the last one. You cannot really keep a pool around and "cleanup" the pool. More work would be needed for that scenario. -- Daniel Kulp [email protected] http://www.dankulp.com/blog
