Well, you could attach a time stamp, that'd be a unique identifier
with a significance to the order in which it was sent, not really
sure of your use case though.
On Sep 10, 7:02 pm, "Diogo Neves" <[EMAIL PROTECTED]> wrote:
> On Wed, Sep 10, 2008 at 5:09 PM, doug <[EMAIL PROTECTED]> wrote:
>
>
On Wed, Sep 10, 2008 at 5:09 PM, doug <[EMAIL PROTECTED]> wrote:
>
> On Sep 10, 11:00 am, Matt Foster <[EMAIL PROTECTED]> wrote:
> > You could use a queue of requests, such that 6 won't be sent until 5
> > has returned. It puts a bit of a bottleneck on the XHRs but will
> > maintain a stable sequ
On Sep 10, 11:00 am, Matt Foster <[EMAIL PROTECTED]> wrote:
> You could use a queue of requests, such that 6 won't be sent until 5
> has returned. It puts a bit of a bottleneck on the XHRs but will
> maintain a stable sequence. I've written an article on how to
> approach something like this,
You could use a queue of requests, such that 6 won't be sent until 5
has returned. It puts a bit of a bottleneck on the XHRs but will
maintain a stable sequence. I've written an article on how to
approach something like this, review at your leisure,
http://positionabsolute.net/blog/2007/04/ajax-
