Ah!
Here's where an applet wins the match. (check this out K.V.)
An applet 'knows' when it is "destroyed()", as opposed to a web page.
Soumya Sankar Basu, I had a similar requirement as I think you have.
The user was required to fill out, sometimes 25 screens of data, not
a lot of data but tedious input. The requirement was, if the user
wasn't finished in one sitting, he could quit the applet and come back
again and continue where he left off.
Better than just quitting I allowed the user to rudely destroy the applet,
like when you close the browser.
In the applet destroy event I would collect up what he had inputted and send it
to
a servlet that wrote a cookie to the client. If too many data for a cookie,
I would write the data to a database table with his userid as
the primary key. The user always has to login anyway for these applets.
When the user came back to continue data entry, I would first get his cookie,
or DB data, as the case may be.
Now try to do it that simply with a browser and HTML forms.
As an added advantage the applet allowed me to organize the data better for
input. Some of the data had relationships that I could handle in the applet
that
were impossible to do using HTML forms.
I still believe, if your requirements dictate more than very simple
interactivity
you are better off with an applet.
Sans adieu,
Danny Rubis
Nic Ferrier wrote:
> >>> Soumya Sankar Basu <[EMAIL PROTECTED]> 30-Jan-00 4:41:33 AM
> >>>
>
> >I have used session persistence for that. In session I keep user id
> and
> >page proceeding. After every time login I check for the previous
> sessions
> >from the session context, if any session exists for the user, I do
> use that
> >session.
>
> Session contexts are no longer supported in many servlet engines
> because they have been depreceated in the API.
>
> >As of now it seems to be working fine. I tried for apache.
>
> JServ still supports this I think because JServ it still supporting
> version 2.0 of the servlet API. Current version is 2.2.
>
> >Or is there any better way to implement this?
>
> Can't you serliaze the objects in the session rather than the
> session?
>
> Serialize the objects to a single file named by the userid and then
> when the user logs in read in the object and add them to a new
> session.
>
> This seems better than the way you're doing it now.
>
> Nic Ferrier
>
> ___________________________________________________________________________
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
> of the message "signoff SERVLET-INTEREST".
>
> Archives: http://archives.java.sun.com/archives/servlet-interest.html
> Resources: http://java.sun.com/products/servlet/external-resources.html
> LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
