This content has been marked as final. Show 3 replies
For others who may be reading this thread (and to express thanks/credit where appropriate, the following was provided by the ColdFusion guru himself:
benforta: you can use the same thing, if you set a SESSION on the CF server and the id and token will get set, as RemoteObject uses HTTP
benforta: But, generally, most session stuff in a CF/Flex app belongs on the client, with the exception of actual logged in state
me: so if RemoteObject uses HTTP is it correct to say 1) the connection is not a constant channel and 2) the CFID, CFToken cookie "header" should be attached to every RemoteObject communication?
benforta: AMF is client initiated over HTTP via the browser
me: and this CFID,CFToken "header" accompanying every AMF message is that set by the cookie installed into the browser by (say) the index.cfm page which loaded the flex app (ie and NOT a second CFID,CFToken allocation assigned by CF to the flex app as say a flex stored object)?
benforta: correct, any cookies shoudl get sent back by the browser with any HTTP request, and an AMF request is an HTTP request
benforta: So long as it is the same domain (and path if appropriate), same rules as any browser conten
me: Have you any idea how this would translate to an AIR app?
benforta: whole different animal there, requests are not originating in a browser, will be trickier