Actually, in the normal case, I just use normal cookies (i.e. stored to disk like you write below).
Does it happen often that a user has cookies disabled or a client does not support cookies? Or am I being too paranoid, here? > -----Original Message----- > From: Johan Compagner [mailto:[EMAIL PROTECTED] > Sent: 31 July 2007 20:04 > To: [email protected]; [EMAIL PROTECTED] > Subject: Re: Testing for cookie capability > > > i guess you want to set a cookie that is stored on disc on the client? > because setting a cookie that is a session cookie doesn't really make much > sense > except if you really also don't create a http session./wicket session > > But if it is a stored cookie then appending it to the url doesn't > make much > sense because > that won't tell you anything the next time. > > johan > > > On 7/31/07, David Leangen <[EMAIL PROTECTED]> wrote: > > > > > > > Looking at the logic, even if I set my own cookies and/or piggyback on > > > the jsessionid value, there is still the case of the first > visit (since > > > no values are set, so I don't know if it's just the first visit, or a > > > client with no cookie capability). > > > > Ok... that's just not true. > > > > Looks like wicket already uses the technique you mentioned. > > > > So, piggybacking works just great! > > > > > > Thanks again, Igor. > > > > > > Cheers, > > Dave > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
