Whoa!
thanx a lot.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4027678#4027678
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4027678
___
jboss-user mailing list
jboss-user
You want to configure the max pool size value for the callback client invoker
on the server side. The configuration map you pass to the server side
Connector will get passed to the server invoker, which will pass it to the
callback client invoker when you add a callback listener. In other words
anonymous wrote : If you need to preserve determinism, you can configure the
connection pool to have no more than one connection by setting
org.jboss.remoting.transport.MicroSocketClientInvoker.MAX_POOL_SIZE_FLAG to "1"
in the Client's configuration map.
Exactly where should I put this configu
Hi :-)
Thank you very much for the reply.
1. The callbacks delivering order is very important in my app, so I really need
determinism.
I'm using push callbacks and the socket transport, so I will configure the
connection pool as you say.
2. I didn't know that you can put a personalized ses
Hi,
anonymous wrote :
| 1. When the server sends callbacks to the client, are the callbacks
delivered in the same order they have been sent?
|
1. Pull callbacks are retrieved in the order that the ServerInvocationHandler
passes them by way of InvokerCallbackHandler.handleCallback().
2.
