Re: Alternative to Cookie during a Session Timeout
Re: Alternative to Cookie during a Session Timeout
- Subject: Re: Alternative to Cookie during a Session Timeout
- From: "Papai Roy" <email@hidden>
- Date: Wed, 24 May 2006 17:54:43 -0700
Hi Chuck,
I think they are in different R-R loop. I added a new NSDictionary in
the userInfo of the response generate from the Main.java. But when I
am trying to print the request / response in the exception method of
Application.java it gives me the userInfo as null:
Main.java:
==========
public void appendToResponse(WOResponse r, WOContext c){
// super.appendToResponse(r,c);
//WORequest rQ = (WORequest)c.request() ;
r.setUserInfo(new NSDictionary(new String("apertuure"),new
String("grpcode")));
super.appendToResponse(r,c);
System.out.println("COMPONENT ACTION URL :: "+c) ;
}
Please let me where am I going wrong
Thanking you in advance.
Roy
On 5/24/06, Chuck Hill <email@hidden> wrote:
On May 24, 2006, at 5:10 PM, Papai Roy wrote:
> Hi Chuck,
> Thanks for the suggestion.
> I have a small doubt here. If I am encoding this code in the URL and
> the session terminates and the exception is catched in
> handleSessionRestoration... method will I be able to retrieve the code
> back. As per my knowledge it will create a new request-response loop
> and my encoded URl will be gone. Please clarify.
>
You can get it from context().request(). The exception is handled in
the same R-R loop, not a new one.
Chuck
> On 5/24/06, Chuck Hill <email@hidden> wrote:
>>
>> On May 24, 2006, at 3:19 PM, Papai Roy wrote:
>>
>> > Hi all,
>> > I am pecuiliar scenario. I am looking for an alternative to cookie
>> > during a session timeout.
>> >
>> > My requirement is to store a particular code somewhere (other
>> than a
>> > cookie) so that when a session time occurs the application read
>> this
>> > code in the handleSessionRestoration... method and regenerates the
>> > correct page with the correct state back again from the code.
>> > Implementing a cookie will serve the purpose but there are
>> limitations
>> > which is restricting to implement it.
>> >
>> > If anyone has any solution to this problem or has implemented
>> > something please do let me know.
>> >
>> You don't have a whole lot of choices here. HTTP only sends three
>> things:
>> 1. The URL, which may contain form values
>> 2. The headers, which would contain cookies
>> 3. The content in the case of a posted form
>>
>> Which comes down to either cookies or form values on the URL. As you
>> can't use cookies, you will have to encode the needed state into the
>> URL.
>>
>> Chuck
>>
>> --
>> Coming in 2006 - an introduction to web applications using WebObjects
>> and Xcode http://www.global-village.net/wointro
>>
>> Practical WebObjects - for developers who want to increase their
>> overall knowledge of WebObjects or who are trying to solve specific
>> problems. http://www.global-village.net/products/
>> practical_webobjects
>>
>>
>>
>>
>>
>
--
Coming in 2006 - an introduction to web applications using WebObjects
and Xcode http://www.global-village.net/wointro
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems. http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden