Asanka
Primary reason is that and I can add few more use cases
1. Acceptor can send messages for a specific session before sending
messages from the initiator (fills, corrections and acknowledgments
for the previously posted transactions).
2. FIX recovery happens with the session creation, so with the current
implementation recovery has to wait till the first message sends.
Around how many of these "sessions" will a typical usecase have? in the
order of services deployed, or a small fixed number - like the JMS
connection factories? If this is a small fixed number, you could define
this similarly to the way the JMS sender defines connection pools
asankha
Andreas Veithen wrote:
As far as I understand the requirement is as follows: When the
transport sender transmits the first message to a given endpoint, it
needs to create a session with the endpoint. This operation is
expensive and causes a delay if the message is received and forwarded
by a proxy service. Since Synapse knows about the endpoints it will
connect to, the idea is to create these sessions in advance (at
startup) so that the proxy service will forward the first message
without delay. However the transports can't get access to the
required information because it is managed by Synapse specific classes.
On 29 juin 08, at 18:15, Asankha C. Perera wrote:
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Asankha C. Perera
WSO2 - http://wso2.org
http://esbmagic.blogspot.com
