That will fix it, at the expense of some more memory for caching.
Why not
just update the page directly in JavaScript? I'm not sure if that is
possible, but it might be another solution. I use that when using a
popup
to choose an object that populates text fields.
Chuck
At 05:05 PM 08/12/2004 -0600, James Cicenia wrote:
I have precisely determined that the javascript is the culprit:
<SCRIPT LANGUAGE=Javascript>window.opener.location.href =
window.opener.location.href;self.close();</SCRIPT>
I have not been using cookies.. well I never set anything to use
them. And
my URLs all show session ids.
Is there something I can put in the javascript to keep the Session?
OR, do
I just setPageCacheSize(100) ?
I can't believe someone would enter more than a 100 items in a popup
before
doing something else. Since
the default is 30 as per the docs, and this is happening rarely,
maybe this
is the solution.
-James Cicenia
On Dec 8, 2004, at 4:55 PM, Chuck Hill wrote:
That is all client side. It appears to trigger a new request to the
server. As to whether the cookies (if that is what you are using) are
sent... Who knows? Log them out in dispatchRequest and see. Seems
like
it should be fine. I don't see why you need a new page to do that
though.
Chuck
At 04:30 PM 08/12/2004 -0600, James Cicenia wrote:
OK - That was a good test actually! My popup window upon save causes
the
backtrack message immediately!
Ah Ha!! My popups are using a trick from Jonathon Rochkind if I am not
mistaken. The way it works
is that upon clicking the save button the popup the followup page is a
blank page with just a small
piece of javascript:
<SCRIPT LANGUAGE=Javascript>window.opener.location.href =
window.opener.location.href;self.close();</SCRIPT>
This then closes the window and then refreshes the parent page. My
question
is... since it has no components on it
at all does WebObject think it is in the same session? Does this make
sense?
-James Cicenia
On Dec 8, 2004, at 3:49 PM, Chuck Hill wrote:
No that would not help. But it would make it a lot worse!
:-)
At 03:35 PM 08/12/2004 -0600, James Cicenia wrote:
Could setting setPageCacheSize(1) help here???
This error and the corresponding docs are a bit confusing to me.
-James Cicenia
On Dec 8, 2004, at 3:14 PM, Dov Rosenberg wrote:
I have seen that occur when someone logs into an app in one window,
but then
they bring up a second window (for the same browser) and login or do
something. If you go back to the first window that is when the error
usually
shows up.
I think it has to do with cookies that are set by WO somewhere along
the
line. It doesn't seem to happen if I open a new browser window with a
different brand of browser, i.e. Using Safari and Firefox seems OK.
I sometimes see it in our app if I am logged into our management
console in
one tab, and then open a new tab and go to a web site and authenticate
myself in the web site. If I go back to the management console and do
something I usually get the same error.
When I do demo's I just use 2 different browsers and avoid the
problem.
I would be interested in a better solution.
-- Dov Rosenberg
Conviveon Corporation
--
Chuck Hill email@hidden
Global Village Consulting Inc.
http://www.global-village.net
<<<<
--
Chuck Hill email@hidden
Global Village Consulting Inc.
http://www.global-village.net
<<<<
--
Chuck Hill email@hidden
Global Village Consulting Inc.
http://www.global-village.net
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
This email sent to email@hidden