Re: Shutting off WOSID ?
Re: Shutting off WOSID ?
- Subject: Re: Shutting off WOSID ?
- From: Kieran Kelleher <email@hidden>
- Date: Sat, 21 Apr 2007 14:05:27 -0400
AFAIK, he will still have the problem of sessions being created
somewhere. WOHyperlink automatically adds the wosid if a session
exists .... it won't add it if there is no session. Follow mikes
advice......... do a stacktrace in Session awake and that will tell
you what is triggering the creation of a session.
Kieran
On Apr 21, 2007, at 11:55 AM, Geoff Hopson wrote:
I've been out the WO loop for a while, but don't you put
?wosid = false;
as a WOHyperlink binding?
On 21/04/07, James Cicenia <email@hidden> wrote:
Hmm -
I put in Miguel's reminder and I just can't get WOHyperlink to not
add a wosid.
here is my simple binding:
Hyperlink1: WOHyperlink {
?resource = aResource.encodedGlobalID;
actionClass = "Display";
}
And, I can't find an instance of the action method in any of my
bindings for that page.
Next?
- jjc
On Apr 21, 2007, at 9:24 AM, Mike Schrag wrote:
> Miguel's reminder is probably what you're missing ... WOHyperlink
> with "directActionName" is fine (it's explicitly designed for
> this). WOHyperlink with "action" is the one you want to avoid.
>
> ms
>
> On Apr 21, 2007, at 10:23 AM, James Cicenia wrote:
>
>> OK -
>>
>> Back to wosid. I am thinking it is my WOHyperlink as I am using
>> its directActionName binding. Why would that want or need an
wosid?
>>
>> otherwise:
>>
>> Is there a simple static call somewhere where I can get the full
>> url up to and including the "wa" part?
>>
>> thanks
>> jc
>>
>> On Apr 21, 2007, at 8:20 AM, Mike Schrag wrote:
>>
>>> 1) If you have anything in the page that requires a session, it
>>> will generate sessions for everything. For instance, you can't
>>> have any component actions anywhere on your page. The easiest
>>> way to do this is to just put a Thread.dumpStack() in your
>>> session constructor, and you'll see pretty fast where they are
>>> being created.
>>>
>>> 2) Data in context userInfo lives for the life of a single
>>> context (/sort of/ equivalent to a single request), and the
>>> session lives across many contexts. If you want data persistent
>>> across multiple requests, you have two options -- WOSession or
>>> manually pass all your state around all the time.
>>>
>>> ms
>>>
>>> On Apr 21, 2007, at 9:11 AM, James Cicenia wrote:
>>>
>>>> Hello -
>>>>
>>>> I have been trying to convert my app to be Direct Action only
>>>> with no session.
>>>>
>>>> 1) My first page renders great. Then we a user clicks on
>>>> anything to go to a
>>>> second page, all the links on the second page get appended a
>>>> WOSID ?
>>>> Why? I have removed the word session from my code and wod files
>>>> wherever
>>>> I could.
>>>>
>>>> 2) What is the difference in storing things in the a subclass of
>>>> context vs session?
>>>>
>>>> Thanks
>>>> James Cicenia
>>>> _______________________________________________
>>>> Do not post admin requests to the list. They will be ignored.
>>>> Webobjects-dev mailing list (Webobjects-
email@hidden)
>>>> Help/Unsubscribe/Update your Subscription:
>>>> 40mdimension.com
>>>>
>>>> This email sent to email@hidden
>>>
>>>
>>> _______________________________________________
>>> Do not post admin requests to the list. They will be ignored.
>>> Webobjects-dev mailing list (email@hidden)
>>> Help/Unsubscribe/Update your Subscription:
>>> 40jimijon.com
>>>
>>> This email sent to email@hidden
>>
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
> 40jimijon.com
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40gmail.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40mac.com
This email sent to email@hidden
_______________________________________________
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