This question is only concerned with BlazeDS AMF remoting using a secure channel (e.g. using HTTPS).
My remoting-config.xml file includes a channel property for scope that is "request" as shown below. I believe this means the server sessions are treated as stateless.
I'm trying to understand the performance penalty created by BlazeDS when implementing secure AMF channel using HTTPS, as it relates to SSL handshakes to establish a connection (my understanding is this handshake is a major contributor to latency for HTTPS connections).
When scope is set to "request" as shown below in remoting-config.xml, will BlazeDS perform an SSL handshake ONCE at the start of a user's session for a web application? In which case, there will be a high latency for the first connection (due to many roundtrips required), but normal latency thereafter because something (I'm not sure what) gets cached (is that right?).
Or, will BlazeDS perform handshakes for EACH and EVERY call between client and server (e.g. from the first call to the 1000'th call)? In which case, there will be high latency throughout the user's entire experience using the web application whenever a server call is issued?
Of course, I hope it's the former case, but I couldn't find any documentation for this. Any comments much appreciated.
Europe, Middle East and Africa