I spent some time fiddling and have a basic jquery/ajax solution to this. I
still don't know how to 'backround' a process, but this will allow a progress
report to be pulled from Django while another view function is busy.
http://www.djangosnippets.org/snippets/994/
hth,
\d
--~--~-~--
Sweet, thank you for all the help guys!
I'll go through all this and figure out which best suits my needs.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to dj
2008/8/20 Julien Phalip <[EMAIL PROTECTED]>:
>
>> If the view is running a loop - how would you provide a variable to another
>> view (that Ajax is calling) about the situation? Let's say a percentage
>> complete -- I immediately think of a global variable, but am not sure how
>> this works in a
On Wednesday, 20 August 2008 15:27:24 Julien Phalip wrote:
> You could use the cache by setting a key that the other view can look
> up.
Right, thanks-- I'll go look it up.
\d
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
> If the view is running a loop - how would you provide a variable to another
> view (that Ajax is calling) about the situation? Let's say a percentage
> complete -- I immediately think of a global variable, but am not sure how
> this works in a multi-user web situation.
You could use the cache
> You could use Ajax for this. The client could periodically (say, every
> second) send a request to the server asking if the calculation is
> over.
If the view is running a loop - how would you provide a variable to another
view (that Ajax is calling) about the situation? Let's say a percentag
On Wed, Aug 20, 2008 at 4:16 PM, coulix <[EMAIL PROTECTED]> wrote:
> Yes, if you can check the Restfull book from Oreilly there is a good
> example on using
> a queue system to submit lengthy job. You submit the work and it gives
> you back an url
> that you can check 'repeatedly' to see the progr
Yes, if you can check the Restfull book from Oreilly there is a good
example on using
a queue system to submit lengthy job. You submit the work and it gives
you back an url
that you can check 'repeatedly' to see the progress or completion of
the job.
Greg
On Aug 20, 5:01 am, Julien Phalip <[EMAI
On Aug 20, 12:15 pm, Graham Dumpleton <[EMAIL PROTECTED]>
wrote:
> That is only half the answer.
>
> Before you get to this point you need a means of backgrounding the
> task to be completed.
You're quite right, I had completely overlooked that side of things ;)
--~--~-~--~~--
On Aug 20, 11:05 am, Julien Phalip <[EMAIL PROTECTED]> wrote:
> Hi,
>
> You could use Ajax for this. The client could periodically (say, every
> second) send a request to the server asking if the calculation is
> over. When the calculation is over, a flag would be set (in the
> server's cache, for
Hi,
You could use Ajax for this. The client could periodically (say, every
second) send a request to the server asking if the calculation is
over. When the calculation is over, a flag would be set (in the
server's cache, for example) and the client would be notified at the
next ajax request.
Tha
Hello,
I've built an app that accepts inputs from the user and then uses them
to do some heavy data crunching. I've got everything working
correctly, however, on some runs the process is too long and the
browser times out before it can complete. Does anyone know a way
around this? Ideally afte
12 matches
Mail list logo
