At 5:02 PM +0200 10/11/07, Per Jessen wrote:
tedd wrote:
For example: If you have a process that is taking time server-side and
want to let the user know in real time what the progress is, this is
one way to do it. That's not something (by definition) you can do with
javascript alone, right
tedd wrote:
> For example: If you have a process that is taking time server-side and
> want to let the user know in real time what the progress is, this is
> one way to do it. That's not something (by definition) you can do with
> javascript alone, right?
Correct, but it doesn't require any ajax
At 8:40 AM +0200 10/11/07, Per Jessen wrote:
tedd wrote:
At 3:27 PM +0200 10/10/07, Per Jessen wrote:
Colin Guthrie wrote:
What do you think of this?
http://webbytedd.com/b/timed-php/
It's a combination of using both ajax and php together.
I'd say overkill for the end result (co
tedd wrote:
> At 3:27 PM +0200 10/10/07, Per Jessen wrote:
>>Colin Guthrie wrote:
>>
What do you think of this?
http://webbytedd.com/b/timed-php/
It's a combination of using both ajax and php together.
>>>
>>> I'd say overkill for the end result (could be done in plain
At 3:27 PM +0200 10/10/07, Per Jessen wrote:
Colin Guthrie wrote:
What do you think of this?
http://webbytedd.com/b/timed-php/
It's a combination of using both ajax and php together.
I'd say overkill for the end result (could be done in plain Javascript
without any "Ajax" calls),
Tha
Colin Guthrie wrote:
>> What do you think of this?
>>
>> http://webbytedd.com/b/timed-php/
>>
>> It's a combination of using both ajax and php together.
>
> I'd say overkill for the end result (could be done in plain Javascript
> without any "Ajax" calls),
That was my reaction too. I've used
6 matches
Mail list logo
