On Thu, 28 May 2015, Lucas Pardue wrote:
My experience developing with libcurl is limited so my thoughts may not
reflect how others would approach HTTP(/2). Just a warning if anything seems
a little odd.
No worries. As entire concept of server pushing is new to everyone in the HTTP
world it
On Thu, May 28, 2015 at 11:26 PM Lucas Pardue
wrote:
> On Thu, 28 May 2015, Daniel Stenberg wrote:
>
> > Thanks. I figure we have to start somewhere. It is easier to discuss and
> argue
> > for and against an existing proposal.
>
> My experience developing with libcurl is limited so my thoughts m
On Thu, 28 May 2015, Daniel Stenberg wrote:
> Thanks. I figure we have to start somewhere. It is easier to discuss and argue
> for and against an existing proposal.
My experience developing with libcurl is limited so my thoughts may not reflect
how others would approach HTTP(/2). Just a warning
On Thu, 28 May 2015, Lucas Pardue wrote:
Interesting proposal.
Thanks. I figure we have to start somewhere. It is easier to discuss and argue
for and against an existing proposal.
Allow me to continue brainstorming on this...
This is how the callback would work:
int curl_stream_push(CURL
Hi Daniel,
Interesting proposal.
> This is how the callback would work:
>
> int curl_stream_push(CURL *newhandle,
> unsigned int stream_id,
> struct curl_push *headers,
> void *userp);
Does stream_id represent the stream the PUSH_
Hi again,
We're in feature-freeze mode for this pending release but that will end with a
release in three weeks and then we'll be open for new features again. I
thought I'd throw some server push ideas in the mean time and see if anyone
has ideas or improvements for them!
I imagine two new o
