I was wondering if it is possible to use HttpInvoker in a stateful interaction with a client?
Eg. suppose I have a service like this...
A client connecting to the above service could expect to have exclusive access to a service instance, which would (presumably) be stored in a HttpSession, so that subsequent method invocations would access the same object.Code:public interface TransactionalService {
public void beginTransaction();
public void putSomeData(.....);
public void putSomeMoreData(.....);
.
.
.
public void finishTransaction();
}
Is such an approach feasible with the current HttpInvoker classes?
And on a second point, is it possible for HttpInvoker to return a reference to another service object, that will be passed by reference rather than by value? This would be similar to how RMI works, but without the pain of setup.
regards,
Scott Russell
