Re: Associating a server push with the original client request

2018-07-15 Thread Alex Osborne
On Sun, 15 Jul 2018, at 9:58 PM, Oleg Kalnichevski wrote: > On Sun, 2018-07-15 at 21:41 +1000, Alex Osborne wrote: > > Here's a simplified example of what I want to do. I want to make two > > requests each having its own directory and save all the corresponding > > responses (both the main

Re: Associating a server push with the original client request

2018-07-15 Thread Oleg Kalnichevski
On Sun, 2018-07-15 at 21:41 +1000, Alex Osborne wrote: > On Sun, 15 Jul 2018, at 8:53 PM, Oleg Kalnichevski wrote: > > On Sun, 2018-07-15 at 16:36 +1000, Alex Osborne wrote: > > > If I receive a server push is it possible to determine which > > > client > > > request it was sent in response to?  >

Re: Associating a server push with the original client request

2018-07-15 Thread Alex Osborne
On Sun, 15 Jul 2018, at 8:53 PM, Oleg Kalnichevski wrote: > On Sun, 2018-07-15 at 16:36 +1000, Alex Osborne wrote: > > If I receive a server push is it possible to determine which client > > request it was sent in response to? > > Not unless the server is willing to help with that. > > Why do

Re: Associating a server push with the original client request

2018-07-15 Thread Oleg Kalnichevski
On Sun, 2018-07-15 at 16:36 +1000, Alex Osborne wrote: > If I receive a server push is it possible to determine which client > request it was sent in response to? Hi Alex Not unless the server is willing to help with that. Why do not you add a correlation id of a sort to the promised request

Associating a server push with the original client request

2018-07-15 Thread Alex Osborne
If I receive a server push is it possible to determine which client request it was sent in response to? I'm not actually after the data of the request just some way to map it back. Some opaque id, object, callback or whatever I can supply with the request and later get back when a push comes in