do not use cookies, use stateless session.
if you still have to use cookies, you should check blazeDS
AppendToGatewayUrl message,
after command message PING / Operation 5, executed.
check message.headers, if name == 'AppendToGatewayUrl' and mustUnderstand ==
true,
save jsession value.
and use jsession value,
requestQueue.push(
{
url: url + jsession,
targetURI: command,
responder: responder,
args: params
}
);
then our friendly message, "Detected duplicate HTTP-based FlexSessions,
generally due to ..." gone, and no double call.
but, if you want to use stateless session, ignore jsession, then you can
force null to royale header.
protected function setRoyaleClientIdOnMessage(message:IMessage):void
{
//var id:String = RoyaleClient.getInstance().id;
//trace("[*setRoyaleClientIdOnMessage] RoyaleClient.getInstance().id: "
+ RoyaleClient.getInstance().id);
//message.headers[AbstractMessage.ROYALE_CLIENT_ID_HEADER] = (id !=
null) ? id : RoyaleClient.NULL_ROYALECLIENT_ID;
message.headers[AbstractMessage.ROYALE_CLIENT_ID_HEADER] =
RoyaleClient.NULL_ROYALECLIENT_ID;
}
and there is no "Detected duplicate HTTP-based FlexSessions, ...", no double
call.
use jwt or paseto or macaroons or others.( I use JPaseto)
and of course, you should aware about session housekeeping,
caused by too many BlazeDS flexSessions creation, hdr(DSId) always null.
i use JS::RemoteObject, because MX::RemoteObject is very "mbulet" (in
Indonesian, meanings Complicated),
there are Channels, Channelset, Operation, AsyncToken and Responders, just
to call a function.
i build latest royale-asjs develop branch using maven, and code with VSCode.
Salam,
Rizal
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
