• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: How to manage long running tasks
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How to manage long running tasks


  • Subject: Re: How to manage long running tasks
  • From: Helge Staedtler <email@hidden>
  • Date: Mon, 05 Dec 2005 12:25:31 +0100

Hi Stefan,

I think I have put together what you might need a time ago. have a look at
www.wocode.com there you will find code and tutorial explaining
LongResponses by example.

http://wocode.com/cgi-bin/WebObjects/WOCode.woa/wa/ShareCodeItem?itemId=291

This way your Session-timeout does not matter, because the page gets
refreshed all the time as long as the response generates results.

Spinning it off in an extra-Thread seems reasonable, but what do you mean
with "Currently, keeping these objects in a DB store seems to be
reasonable."? Images or as you said "real-world big image media files" in
the DB? Sounds like a really bad idea to me.

regards,
Helge

--
Momo was there and joined in, that was all, but for some reason her mere
presence put bright ideas into their heads. -- from Michael Ende's "Momo"

Expect and Respect.


Am 05.12.2005 1:29 Uhr schrieb "Stefan Pantke" unter <email@hidden>:

> I managed to produce printer ready PDF output using
> iText. Although iText can't do anything, it is rich enough
> for my app.
>
> Now I need to start testing using real-world big image media files.
>
> Don't know exactly right now, but I suppose that these calls may
> take some to finish. Probably too much time for my WO default
> environment. I'd like to prepare a solution, which works independently
> of the current WOA timeout settings.
>
> To prepare a general solution, I'd like to spawn a worker thread,
> which takes a job description, computes the result and finally
> puts the results aside.
>
> Does WO have a special technique to de-couple lengthy compute jobs? Or
> should I just spawn a Java-Thread and attach this to my current
> session?
>
> Furthermore, I'd like to prepare some EO objects, which model
> running compute jobs and results.
>
> Currently, keeping these objects in a DB store seems to be reasonable.
>
> In general, I'd like to know, if I may create in-memory EO objects,
> which
> don't get saved to the DB store. Well, this should be possible.
>
> Any ideas how to start reading about this?
>
>  _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list      (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Locking/Unlocking-Problem with EditingContext
      • From: Helge Staedtler <email@hidden>
    • Re: How to manage long running tasks
      • From: Stefan Pantke <email@hidden>
References: 
 >How to manage long running tasks (From: Stefan Pantke <email@hidden>)

  • Prev by Date: JCheckBox in Java Client table
  • Next by Date: Re: How to manage long running tasks
  • Previous by thread: How to manage long running tasks
  • Next by thread: Re: How to manage long running tasks
  • Index(es):
    • Date
    • Thread