-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mon,
Mon Cab wrote: > I think its going to have to be solution 1. All Im really interested > in is user data associated with a session, so I'll probably map userId > to sessionID in the DB and then pull user info when the service sends > me a session id. Here another solution: 1. Create an action that accepts a session id as a parameter. Then, have that action make a loopback call to the web server, but put the session id into the URL (basically, url-encode the session id yourself) and call the action in #2: 2. Create another action that returns the session information you want as, say, XML. 3. Back in your first action, parse the XML and re-format it as HTML. Better yet, throw everything into cocoon and don't write any code yourself. ;) - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFzyZ29CaO5/Lv0PARAqiwAKCOUkKlvLj6oRowTG9NEXWqqRO7rwCgnXzB wWThV4mGneOm8QrxbNn1gJg= =nr6M -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]