Re: [Web-SIG] Inviting feedback on my proposed "ASGI" spec

2016-03-10 Thread Andrew Godwin
On Thu, Mar 10, 2016 at 2:07 PM, Robert Collins wrote: > On 11 March 2016 at 10:34, Andrew Godwin wrote: > >> > >> > >> I realise this may sound bikesheddy, but it would be really good to > >> not call it ASGI. From your docs " > >> Despite the name of the proposal, ASGI does not specify or desi

Re: [Web-SIG] Inviting feedback on my proposed "ASGI" spec

2016-03-10 Thread Robert Collins
On 11 March 2016 at 10:34, Andrew Godwin wrote: >> >> >> I realise this may sound bikesheddy, but it would be really good to >> not call it ASGI. From your docs " >> Despite the name of the proposal, ASGI does not specify or design to >> any specific in-process async solution, such as asyncio, twi

Re: [Web-SIG] Inviting feedback on my proposed "ASGI" spec

2016-03-10 Thread Andrew Godwin
> > > > I realise this may sound bikesheddy, but it would be really good to > not call it ASGI. From your docs " > Despite the name of the proposal, ASGI does not specify or design to > any specific in-process async solution, such as asyncio, twisted, or > gevent. Instead, the receive_many function

Re: [Web-SIG] Inviting feedback on my proposed "ASGI" spec

2016-03-10 Thread Robert Collins
On 10 March 2016 at 13:34, Andrew Godwin wrote: > Hi all, > > As some of you may know, I've been working over the past few months to bring > native WebSocket support to Django, via a project codenamed "Django > Channels" - this is mostly the reason I've been involved in recent WSGI > discussions.

Re: [Web-SIG] Inviting feedback on my proposed "ASGI" spec

2016-03-10 Thread Robert Collins
On 11 March 2016 at 08:32, Andrew Godwin wrote: > > > > > Well, the protocol server would be the thing that's doing the joining if it > sees multiple headers - you'd always see comma-joined headers from clients > as an ASGI application, which I like as I like consistency. For consistency, why not

Re: [Web-SIG] Inviting feedback on my proposed "ASGI" spec

2016-03-10 Thread Andrew Godwin
On Thu, Mar 10, 2016 at 10:57 AM, wrote: > On Thu, 10 Mar 2016, Andrew Godwin wrote: > > I think you're right, and I've just been stubbornly trying to use a dict as >> it's slightly "nicer". I honestly considered making both sides dict and >> cookies the separate thing as they're the only special

Re: [Web-SIG] Inviting feedback on my proposed "ASGI" spec

2016-03-10 Thread chris . dent
On Thu, 10 Mar 2016, Andrew Godwin wrote: I think you're right, and I've just been stubbornly trying to use a dict as it's slightly "nicer". I honestly considered making both sides dict and cookies the separate thing as they're the only special case, but I suspect that multiple headers are one o

Re: [Web-SIG] Inviting feedback on my proposed "ASGI" spec

2016-03-10 Thread Andrew Godwin
On Thu, Mar 10, 2016 at 1:59 AM, Cory Benfield wrote: > > > On 10 Mar 2016, at 00:34, Andrew Godwin wrote: > > > > To that end, I did some work to make the underlying mechanism Django > Channels uses into more of a standard, which I have codenamed ASGI; while > initially I intended for it to be

Re: [Web-SIG] Inviting feedback on my proposed "ASGI" spec

2016-03-10 Thread Ionel Maries Cristian
Hey, On Thu, Mar 10, 2016 at 2:34 AM, Andrew Godwin wrote: > Helpful quick Q&A: http://channels.readthedocs.org/en/latest/inshort.html > I have looked over that and it's not very clear what goes where. [1] I'd be inclined to understand that the process type "that handles HTTP and WebSockets" wo

Re: [Web-SIG] Inviting feedback on my proposed "ASGI" spec

2016-03-10 Thread Cory Benfield
> On 10 Mar 2016, at 00:34, Andrew Godwin wrote: > > To that end, I did some work to make the underlying mechanism Django Channels > uses into more of a standard, which I have codenamed ASGI; while initially I > intended for it to be a Django documented API, as I've gone further with the > pr