|
|
 |
 |
 |
 |
Javascript / Client Side Development
|
 |
 |
 |
 |
|
|
|
|
The Round-Trip Time of an XMLHTTP Call?
Hi.
Can somebody tell me how to tell how long the round trip
will take from client to server and back of an xmlhttp call?
I want to gauge how long the server code is going to crunch
and return the value to the client so I can set the setTimeout()
msec value appropriately.
thanks for any feedback.
Hi.
Can somebody tell me how to tell how long the round trip
will take from client to server and back of an xmlhttp call?
I want to gauge how long the server code is going to crunch
and return the value to the client so I can set the setTimeout()
msec value appropriately.
thanks for any feedback.
Hi.
Can somebody tell me how to tell how long the round trip
will take from client to server and back of an xmlhttp call?
I want to gauge how long the server code is going to crunch
and return the value to the client so I can set the setTimeout()
msec value appropriately.
thanks for any feedback.
pbd22 said the following on 5/21/2007 12:56 PM:
> Hi. > Can somebody tell me how to tell how long the round trip
> will take from client to server and back of an xmlhttp call?
time than it took you to post the same message three times though.
> I want to gauge how long the server code is going to crunch
> and return the value to the client so I can set the setTimeout()
> msec value appropriately.
Why? Using setTimeout based on how long an XHR call takes is the wrong
way. Use the onreadystate event handler, when the call is finished it
will tell you, then have it trigger the appropriate function.
--
Randy
Chance Favors The Prepared Mind
comp.lang.javascript FAQ - http://jibbering.com/faq/index.html
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/
On May 21, 10:10 am, Randy Webb <HikksNotAtH@aol.com> wrote:
> pbd22 said the following on 5/21/2007 12:56 PM: > > Hi.
> > Can somebody tell me how to tell how long the round trip
> > will take from client to server and back of an xmlhttp call?
> From the time it starts until the time it ends. Typically it is less
> time than it took you to post the same message three times though.
> > I want to gauge how long the server code is going to crunch
> > and return the value to the client so I can set the setTimeout()
> > msec value appropriately.
> Why? Using setTimeout based on how long an XHR call takes is the wrong
> way. Use the onreadystate event handler, when the call is finished it
> will tell you, then have it trigger the appropriate function.
> --
> Randy
> Chance Favors The Prepared Mind
> comp.lang.javascript FAQ -http://jibbering.com/faq/index.html
> Javascript Best Practices -http://www.JavascriptToolbox.com/bestpractices/
thanks, that was what i needed.
On May 21, 11:10 am, Randy Webb <HikksNotAtH@aol.com> wrote:
> > Can somebody tell me how to tell how long the round trip > > will take from client to server and back of an xmlhttp call? > From the time it starts until the time it ends. Typically it is less
> time than it took you to post the same message three times though.
pbd22 said the following on 5/21/2007 3:26 PM:
> On May 21, 10:10 am, Randy Webb <HikksNotAtH @aol.com> wrote: >> pbd22 said the following on 5/21/2007 12:56 PM: >>> Hi.
>>> Can somebody tell me how to tell how long the round trip
>>> will take from client to server and back of an xmlhttp call?
>> From the time it starts until the time it ends. Typically it is less
>> time than it took you to post the same message three times though.
>>> I want to gauge how long the server code is going to crunch
>>> and return the value to the client so I can set the setTimeout()
>>> msec value appropriately.
>> Why? Using setTimeout based on how long an XHR call takes is the wrong
>> way. Use the onreadystate event handler, when the call is finished it
>> will tell you, then have it trigger the appropriate function.
>> --
>> Randy
>> Chance Favors The Prepared Mind
>> comp.lang.javascript FAQ -http://jibbering.com/faq/index.html
>> Javascript Best Practices -http://www.JavascriptToolbox.com/bestpractices/
> not sure why that happened.
to that is simple - because you posted it three times.
Better question:
What is it about Google Groups that makes newbes go brain dead?
--
Randy
Chance Favors The Prepared Mind
comp.lang.javascript FAQ - http://jibbering.com/faq/index.html
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/
On May 21, 2:44 pm, Randy Webb <HikksNotAtH@aol.com> wrote:
> pbd22 said the following on 5/21/2007 3:26 PM: > > On May 21, 10:10 am, Randy Webb <HikksNotAtH@aol.com> wrote:
> >> pbd22 said the following on 5/21/2007 12:56 PM:
> >>> Hi.
> >>> Can somebody tell me how to tell how long the round trip
> >>> will take from client to server and back of an xmlhttp call?
> >> From the time it starts until the time it ends. Typically it is less
> >> time than it took you to post the same message three times though.
> >>> I want to gauge how long the server code is going to crunch
> >>> and return the value to the client so I can set the setTimeout()
> >>> msec value appropriately.
> >> Why? Using setTimeout based on how long an XHR call takes is the wrong
> >> way. Use the onreadystate event handler, when the call is finished it
> >> will tell you, then have it trigger the appropriate function.
> >> --
> >> Randy
> >> Chance Favors The Prepared Mind
> >> comp.lang.javascript FAQ -http://jibbering.com/faq/index.html
> >> Javascript Best Practices -http://www.JavascriptToolbox.com/bestpractices/
> > not sure why that happened.
> Why what happened? That you posted the message three times? The answer
> to that is simple - because you posted it three times.
> Better question:
> What is it about Google Groups that makes newbes go brain dead?
> --
> Randy
> Chance Favors The Prepared Mind
> comp.lang.javascript FAQ -http://jibbering.com/faq/index.html
> Javascript Best Practices -http://www.JavascriptToolbox.com/bestpractices/
I posted. I hit submit several times with no reaction (no indication
that the browser was working). Then, there were three posts. I have
posted here several times (some of which you have responded to) and it
is clear that I do not repost on purpose. I have been quite pleasant
in this thread despite the fact that you have been rude. You are not
the only guy in the world that knows JavaScript - if you are going to
be rude, I'd appreciate it if you don't reply.
pbd22 said the following on 5/21/2007 6:23 PM:
> On May 21, 2:44 pm, Randy Webb <HikksNotAtH @aol.com> wrote: >> pbd22 said the following on 5/21/2007 3:26 PM: >>> On May 21, 10:10 am, Randy Webb <HikksNotAtH@aol.com> wrote:
>>>> pbd22 said the following on 5/21/2007 12:56 PM:
>>>>> Hi.
>>>>> Can somebody tell me how to tell how long the round trip
>>>>> will take from client to server and back of an xmlhttp call?
>>>> From the time it starts until the time it ends. Typically it is less
>>>> time than it took you to post the same message three times though.
>>>>> I want to gauge how long the server code is going to crunch
>>>>> and return the value to the client so I can set the setTimeout()
>>>>> msec value appropriately.
>>>> Why? Using setTimeout based on how long an XHR call takes is the wrong
>>>> way. Use the onreadystate event handler, when the call is finished it
>>>> will tell you, then have it trigger the appropriate function.
>>>> --
>>>> Randy
>>>> Chance Favors The Prepared Mind
>>>> comp.lang.javascript FAQ -http://jibbering.com/faq/index.html
>>>> Javascript Best Practices -http://www.JavascriptToolbox.com/bestpractices/
>>> not sure why that happened.
>> Why what happened? That you posted the message three times? The answer
>> to that is simple - because you posted it three times.
>> Better question:
>> What is it about Google Groups that makes newbes go brain dead?
> Actually, the browser froze (due to other work on this computer) when
> I posted. I hit submit several times with no reaction (no indication
> that the browser was working). Then, there were three posts.
> I have posted here several times (some of which you have responded to)
> and it is clear that I do not repost on purpose.
I had no reason to research it before but checking it, that is correct.
> I have been quite pleasant in this thread despite the fact that you have
> been rude.
I don't apologize often so bookmark it, but you have my apology.
--
Randy
Chance Favors The Prepared Mind
comp.lang.javascript FAQ - http://jibbering.com/faq/index.html
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/
On May 21, 8:33 pm, Randy Webb <HikksNotAtH@aol.com> wrote:
> pbd22 said the following on 5/21/2007 6:23 PM: > > On May 21, 2:44 pm, Randy Webb <HikksNotAtH@aol.com> wrote:
> >> pbd22 said the following on 5/21/2007 3:26 PM:
> >>> On May 21, 10:10 am, Randy Webb <HikksNotAtH@aol.com> wrote:
> >>>> pbd22 said the following on 5/21/2007 12:56 PM:
> >>>>> Hi.
> >>>>> Can somebody tell me how to tell how long the round trip
> >>>>> will take from client to server and back of an xmlhttp call?
> >>>> From the time it starts until the time it ends. Typically it is less
> >>>> time than it took you to post the same message three times though.
> >>>>> I want to gauge how long the server code is going to crunch
> >>>>> and return the value to the client so I can set the setTimeout()
> >>>>> msec value appropriately.
> >>>> Why? Using setTimeout based on how long an XHR call takes is the wrong
> >>>> way. Use the onreadystate event handler, when the call is finished it
> >>>> will tell you, then have it trigger the appropriate function.
> >>>> --
> >>>> Randy
> >>>> Chance Favors The Prepared Mind
> >>>> comp.lang.javascript FAQ -http://jibbering.com/faq/index.html
> >>>> Javascript Best Practices -http://www.JavascriptToolbox.com/bestpractices/
> >>> not sure why that happened.
> >> Why what happened? That you posted the message three times? The answer
> >> to that is simple - because you posted it three times.
> >> Better question:
> >> What is it about Google Groups that makes newbes go brain dead?
> > Actually, the browser froze (due to other work on this computer) when
> > I posted. I hit submit several times with no reaction (no indication
> > that the browser was working). Then, there were three posts.
> Fair enough.
> > I have posted here several times (some of which you have responded to)
> > and it is clear that I do not repost on purpose.
> I had no reason to research it before but checking it, that is correct.
> > I have been quite pleasant in this thread despite the fact that you have
> > been rude.
> I don't apologize often so bookmark it, but you have my apology.
> --
> Randy
> Chance Favors The Prepared Mind
> comp.lang.javascript FAQ -http://jibbering.com/faq/index.html
> Javascript Best Practices -http://www.JavascriptToolbox.com/bestpractices/
the advice, your suggestion was very useful.
Kind regards,
Peter
|
|
|
|
|
|
Add to del.icio.us |
Digg this |
Stumble it |
Powered by Megasolutions Inc