Re: MOD_PLSQL and cookies - when available to the server?

In message <5I2dnQBkuYP3UeTenZ2dnUVZ_vudnZ2d_at_comcast.com> , Mark C. Stock <mcstockX_at_Xenquery.com> writes
>
>"Andy Hardy" <junkmail@[127.0.0.1]> wrote in message
>news:pr9tOfFbTZeDFAAh@[127.0.0.1]...
>> In message <-d2dnRGTb7Hd0-TeRVn-uQ_at_comcast.com> , Mark C. Stock
>> <mcstockX_at_Xenquery.com> writes
>>>
>...
>
>>>presumably you're using OWA_COOKIE.SEND to set the cookie
>>>
>>>is OWA_COOKIE.GET not retrieving the value?
>>
>> We are, but the current application does an HTTP 'send' on completion of
>> the logon. This transfers the cookie to the client browser and makes it
>> available to later 'gets'. I was hoping that the new URL/procedure would
>> be able to 'send' the cookie and have it available for 'get' *before* I'd
>> actually done the HTTP 'send' to the client.
>>
>
>...
>
>> --
>> Andy Hardy. PGP ID: 0xA62A4849
>
>still not quite following you, but i'm quessing you want to call a PL/SQL
>procedure that can get the cookie contents after the Set-Cookie line is
>generated but before the cookie is known to the browser (hence, before
>OWA_COOKIE.GET can see it)
>

Correct.

>if that's the case, two options come to mind:

Thanks, I'll look into them. Once of my concerns is the way in which mod_plsql handles the pooling of connections, etc. I'm not entirely sure when it's safe to write to the global packages, etc. and knowing that the current set of values refer to the current client and not to the previous one...

-- 
Andy Hardy. PGP ID: 0xA62A4849