I haven't actually done this yet (but am planning to) -- however, can't
you take care of this behavior with dhtml??  It seems like you could
call a javascript function on submit that pulled a layer (actully
css-pos) to the top.  That layer would say "in progress" with a pretty
animated gif or have some neat little javascript progress bar.  The
javascript would then submit the form.  When it's done, the browser
updates.  This seems like it will work and is likely better than the
server side solutions.  Is there something I'm missing??  BTW, I think
this is how expedia used to do it.

LES

-----Original Message-----
From: Mike Cannon-Brookes [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, June 25, 2003 7:01 PM
To: [EMAIL PROTECTED]
Subject: Re: [OS-webwork] Displaying a progress page

Uhm, well why not just make your task runnable and run it in a new
thread?
:) Or you could use a util.Timer.

Another (nicest IMHO) alternative is to make it a scheduled task and use
something like Quartz to kick it off.

M

On 26/6/03 6:05 AM, "Jason Carreira" ([EMAIL PROTECTED]) penned
the
words:

> Well, for us we queue a JMS message. I'm not sure of another way to
> start an asynch process in the J2EE spec....
> 
>> -----Original Message-----
>> From: Lars Fischer [mailto:[EMAIL PROTECTED]
>> Sent: Wednesday, June 25, 2003 3:42 PM
>> To: [EMAIL PROTECTED]
>> Subject: RE: [OS-webwork] Displaying a progress page
>> 
>> 
>> Jason,
>> 
>> thanks for the reply !
>> 
>> Any hint how you start the asynchronous process ?
>> 
>> Lars
>> 
>>> If you can start it up as an asynchronous process, you can use the
>>> trick of having a progress page which checks some state, such as a
>>> database or something in the session, and shows the progress bar or
>>> just a "processing..." and have it refresh itself using a
>> meta-refresh 
>>> if things aren't done... If the process is done you can
>> forward to a 
>>> final status page.
>>> 
>>> We've used this technique pretty successfully.
>>> 
>>> Jason
>>> 
>>>> -----Original Message-----
>>>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>>>> Sent: Wednesday, June 25, 2003 8:31 AM
>>>> To: [EMAIL PROTECTED]
>>>> Subject: [OS-webwork] Displaying a progress page
>>>> 
>>>> 
>>>> Does anyone have a good idea how to display a temporary
>>>> progress page in WW 1.x ?
>>>> 
>>>> I have a form where users can define paremeters for an import
>>>> of data into the local database. After submitting the page
>>>> the import method is started. This process may take a while
>>>> so I want to show a general progress page saying that
>>>> the import is running. After finishing the import I want to
>>>> return to the original page where users can start an import.
>>>> 
>>>> Does anyone know how to do this ? The problem seems to be
>>>> that WW is displaying the result-view AFTER the whole action
>>>> has finished.
>>>> 
>>>> Thanks in advance
>>>> 
>>>> Lars
>>>> 
>>>> 
>>>> 
>>>> -------------------------------------------------------
>>>> This SF.Net email is sponsored by: INetU
>>>> Attention Web Developers & Consultants: Become An INetU
>>>> Hosting Partner. Refer Dedicated Servers. We Manage Them. You
>>>> Get 10% Monthly Commission! INetU Dedicated Managed Hosting
>>>> http://www.inetu.net/partner/index.php
>>>> 
>>>> _______________________________________________
>>>> Opensymphony-webwork mailing list
>>>> [EMAIL PROTECTED]
>>>> https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
>>>> 
>>> 
>>> 
>>> -------------------------------------------------------
>>> This SF.Net email is sponsored by: INetU
>>> Attention Web Developers & Consultants: Become An INetU Hosting
>>> Partner. Refer Dedicated Servers. We Manage Them. You Get
>> 10% Monthly 
>>> Commission! INetU Dedicated Managed Hosting
>>> http://www.inetu.net/partner/index.php
>>> _______________________________________________
>>> Opensymphony-webwork mailing list
>>> [EMAIL PROTECTED]
>>> https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
>>> 
>> 
>> 
>> 
>> -------------------------------------------------------
>> This SF.Net email is sponsored by: INetU
>> Attention Web Developers & Consultants: Become An INetU
>> Hosting Partner. Refer Dedicated Servers. We Manage Them. You
>> Get 10% Monthly Commission! INetU Dedicated Managed Hosting
>> http://www.inetu.net/partner/index.php
>> 
>> _______________________________________________
>> Opensymphony-webwork mailing list
>> [EMAIL PROTECTED]
>> https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
>> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: INetU
> Attention Web Developers & Consultants: Become An INetU Hosting
Partner.
> Refer Dedicated Servers. We Manage Them. You Get 10% Monthly
Commission!
> INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
> _______________________________________________
> Opensymphony-webwork mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork



-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork


-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork

Reply via email to