On Oct 22, 3:44 am, Javier Guerra wrote:
> On Wed, Oct 21, 2009 at 9:49 AM, Michael Thon wrote:
> > Thanks for pointing me towards celery. Its probably overkill for what
> > I want to do right now but I'm going to try to set it up anyway.
>
> the
On Oct 21, 6:44 pm, Javier Guerra wrote:
> On Wed, Oct 21, 2009 at 9:49 AM, Michael Thon wrote:
> > Thanks for pointing me towards celery. Its probably overkill for what
> > I want to do right now but I'm going to try to set it up anyway.
>
> the
On Wed, Oct 21, 2009 at 9:49 AM, Michael Thon wrote:
> Thanks for pointing me towards celery. Its probably overkill for what
> I want to do right now but I'm going to try to set it up anyway.
the roll-your-own alternative is just setting a DB table with the
queued tasks,
On Oct 21, 2009, at 11:55 AM, Daniel Roseman wrote:
>
> On Oct 21, 9:28 am, Mike Thon wrote:
>> I'm new to web programming and I have a basic question about the
>> design of my Django application. my application will do some number
>> crunching on data files uploaded by
On Oct 21, 9:28 am, Mike Thon wrote:
> I'm new to web programming and I have a basic question about the
> design of my Django application. my application will do some number
> crunching on data files uploaded by users. The data processing will
> take from minutes to hours
Use separate background process (daemon) to handle queue + crunching (or
launching crunching). So your web app just posts jobs to background
process and then returns control back to user.
Otherwise your idea is quite correct.
Mike Thon kirjoitti:
> I'm new to web programming and I have a
I'm new to web programming and I have a basic question about the
design of my Django application. my application will do some number
crunching on data files uploaded by users. The data processing will
take from minutes to hours for each job. I don't expect to ever get a
large number of
7 matches
Mail list logo