> I'm no expert on the way this works (or anything in particular for that
matter),
> but I think you really need to get over the fact that you cannot have
multiple
> browser windows partaking in the same session (from the perspective of the
> server). If you think about it, the session exists on the server in order
to keep
> track of what is going on in a specific browser window for a specific
client
> machine. How then can you expect a session to maintain state for multiple
> windows? I don't think you can.
Hmmm.. One user one state seems like a valid expectation in some
circumstances to me... I have a list of Things and a link to pop up a small
"wizard" to add a new Thing.. this seems like a slick and familiar way to do
this... that way the user is able to see what is already in the list of
Things without navigating back... using javascript I can make a little
window with no navigation or scrolls.. it contains a form and a button, when
the button is pressed the info is submitted, the window is closed and the
parent window is refreshed... this all works PERFECT except that the popup
always needs to be authenticated... there must be a way around this without
using url encoding... maybe not... persistent sessions would be great..
having some trouble implementing it... but, damn, am i learning a ton! :)
>
> I think you need to focus on automatically logging the new window in as a
> *NEW* session and then somehow getting it to where you want it to be
> in the application.
Trying to get my head around doing this right now... but there is alot to
understand... Getting a grip on where catalina ends and turbine begins is
taking some doing, but I am getting there... so much source, so little free
time...
"I am just a simple caveman"
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
