Prashanth.S wrote:
But this doesnt solve my problem as it says me to use url rewriting..
Thanks
Prashanth
If you use the Struts tags for generating hyperlinks, you get support
for either for free ... and you as a developer don't have to worry about
doing something special.
Craig
But this doesnt solve my problem as it says me to use url rewriting..
Thanks
Prashanth
Mark Lowe <[EMAIL PROTECTED]> wrote:
I'd have though cookie use was upto the user rather than your client.
http://jakarta.apache.org/struts/userGuide/struts-html.html#link
On Wednesday, October 8, 2003, at 1
I'd have though cookie use was upto the user rather than your client.
http://jakarta.apache.org/struts/userGuide/struts-html.html#link
On Wednesday, October 8, 2003, at 12:16 PM, Prashanth.S wrote:
Hi navjot,
My clients doesnt want me to use cookiesSo that my application
should run even for
Hi navjot,
My clients doesnt want me to use cookiesSo that my application should run even for
users who have disabled cookies...The problem with url-rewriting is that jsessionid is
maintained across applications so that if any one get url of the application they can
go through the applicatio
here is the clue.
cookies are again of two types.
+ persistent - will remain there even if you close browser and opens next
day.
+ non-persistent/session - the moment you close browser window they are
gone. These also work only under child browser windows.
So, i assume you are looking for sessio
Hi navjot,
Thanks for the reply...But the problem with url rewriting is that jsessionid is
maintained across browsers so that users can access the application if they get the
url..[even on other system the application work if u get the url]..so is there any
other option???
Thanks
Prashanth
Nav
Navjot Singh wrote:
theoretcially, there are 3 ways.
1. URL Rewriting
2. Client side Cookies
3. Server side Session (again use cookies but just for an ID)
if you are adamant about not using cookies at any level. URL rewriting is
the only option left.
any other?
Server side Session of course
Hi Prashanth
IMHO if you thinking about these as separate things then you're
thinking wrong. Sessions use url encoding and cookies to maintain
state. But when site building you shouldn't need to drill down this far.
Folks often think it clever to manipulated cookies, cos it looks real
clever..
theoretcially, there are 3 ways.
1. URL Rewriting
2. Client side Cookies
3. Server side Session (again use cookies but just for an ID)
if you are adamant about not using cookies at any level. URL rewriting is
the only option left.
any other?
navjot singh
>-Original Message-
>From: Prash
9 matches
Mail list logo
