[
https://issues.apache.org/jira/browse/SYNAPSE-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vanjikumaran Sivajothy updated SYNAPSE-333:
-------------------------------------------
Fix Version/s: (was: 2.0)
FUTURE
> Proposal to improve/consolidate session-affine load balancing options
> ---------------------------------------------------------------------
>
> Key: SYNAPSE-333
> URL: https://issues.apache.org/jira/browse/SYNAPSE-333
> Project: Synapse
> Issue Type: Improvement
> Affects Versions: 1.2
> Reporter: Eric Hubert
> Fix For: FUTURE
>
>
> Currently we have two options for server-initiated session management and
> only one for client-initiated session management.
> - Server using SOAP header (named SOAP)
> - Server using HTTP header (named Transport)
> - Client using SOAP header with ClientID of Synapse Namespace (named Client
> ID)
> I'd like to propose 4 options for Synapse 1.3 using "speaking names" which
> make it much easier to understand their meaning:
> - Server using SOAP header (named Server - SOAP)
> - Server using HTTP header (named Server - TRANSPORT)
> - Client using SOAP header (named Client - SOAP)
> - Client using HTTP header (named Client - TRANSPORT)
> Doing this I would also like to suggest the renaming of the ClientID to
> ClientSessionID, which will be used either inside the SOAP header or in the
> transport header. If the name is needed to keep backward compatibility,
> ClientID could be deprecated.
> Adding the additional option for client-initiated session management using
> transport headers would enable the usage of this feature combined with
> non-SOAP clients like Hessian clients.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
