You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by Jason Grant <ja...@logular.com> on 2001/04/08 20:18:57 UTC

Page update on job completion

Tips to get me started would be appreciated:

I have a need to present images (graphs) that may take a minute or so to
build.  My intention was to initiate a background "build" Action which
commences when client login succeeds.  The client would gain access to the
images by navigating to another page which presents the graphs.

I want to present a "working..." screen if the images aren't ready when the
user navigates to the graph page (no problem here - an action can flag
readiness).  As each image becomes available however, I'd like to display
new content without forcing the user to hit a "update/reload" button.  Is
this possible, and if so, how?  It's not obvious to me whether I can:

 a) provide the client with new page content asynchronously
 b) have the client quietly poll for updated page content

Apologies if this request relates more to client side than server side (I'm
hoping that I don't have to solve this with javascript).

Thanks,

Jason.


---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org


Re: Page update on job completion

Posted by Jon Stevens <jo...@latchkey.com>.
on 4/13/01 3:09 PM, "Jason Grant" <ja...@logular.com> wrote:

> Can I make turbine respond with an image rather than HTML for particular
> URI, and if so, how? (direct manipulation of HttpResponse?)

RawScreen

Or in the TDK, ImageServer

-jon

-- 
If you come from a Perl or PHP background, JSP is a way to take
your pain to new levels. --Anonymous
<http://jakarta.apache.org/velocity/ymtd/ymtd.html>


---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org


Re: Page update on job completion

Posted by Jason Grant <ja...@logular.com>.
Can I make turbine respond with an image rather than HTML for particular
URI, and if so, how? (direct manipulation of HttpResponse?)

Background: 

I think the proposed "refresh" solution below is flawed because
 - client pull is not supported by all browsers
 - the solution involves polling by the client

Perhaps a cleaner solution would be to return an initial page that comes
back to the servlet for the images:
  <img src="turbine-uri-a">
  <img src="turbine-uri-b">
The servlet can then block on images that aren't ready.

Rather than hit a separate vanilla servlet, I'd like to go back to turbine
for the images, where I get the user/cache/etc management for free.

Thanks,

J.


On 2001.04.08 15:36:45 -0400 Jason Grant wrote:
> Apologies, my enquiry may not have been relevant to this forum.
> 
> I think the answer is 'client pull' using something like:
> 
>   <meta http-equiv="refresh" content="4"
> url="http://host:8080/servlet/whatever">
> 
> 
> J.
> 
> On 2001.04.08 14:18:57 -0400 Jason Grant wrote:
> > Tips to get me started would be appreciated:
> > 
> > I have a need to present images (graphs) that may take a minute or so
> to
> > build.  My intention was to initiate a background "build" Action which
> > commences when client login succeeds.  The client would gain access to
> > the
> > images by navigating to another page which presents the graphs.
> > 
> > I want to present a "working..." screen if the images aren't ready when
> > the
> > user navigates to the graph page (no problem here - an action can flag
> > readiness).  As each image becomes available however, I'd like to
> display
> > new content without forcing the user to hit a "update/reload" button. 
> Is
> > this possible, and if so, how?  It's not obvious to me whether I can:
> > 
> >  a) provide the client with new page content asynchronously
> >  b) have the client quietly poll for updated page content
> > 
> > Apologies if this request relates more to client side than server side
> > (I'm
> > hoping that I don't have to solve this with javascript).
> > 
> > Thanks,
> > 
> > Jason.
> > 
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: turbine-user-help@jakarta.apache.org
> > 
> > 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org


Re: Page update on job completion

Posted by Jason Grant <ja...@logular.com>.
Apologies, my enquiry may not have been relevant to this forum.

I think the answer is 'client pull' using something like:

  <meta http-equiv="refresh" content="4"
url="http://host:8080/servlet/whatever">


J.

On 2001.04.08 14:18:57 -0400 Jason Grant wrote:
> Tips to get me started would be appreciated:
> 
> I have a need to present images (graphs) that may take a minute or so to
> build.  My intention was to initiate a background "build" Action which
> commences when client login succeeds.  The client would gain access to
> the
> images by navigating to another page which presents the graphs.
> 
> I want to present a "working..." screen if the images aren't ready when
> the
> user navigates to the graph page (no problem here - an action can flag
> readiness).  As each image becomes available however, I'd like to display
> new content without forcing the user to hit a "update/reload" button.  Is
> this possible, and if so, how?  It's not obvious to me whether I can:
> 
>  a) provide the client with new page content asynchronously
>  b) have the client quietly poll for updated page content
> 
> Apologies if this request relates more to client side than server side
> (I'm
> hoping that I don't have to solve this with javascript).
> 
> Thanks,
> 
> Jason.
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org