Quantcast
Channel: Considering ASGI support
Browsing latest articles
Browse All 24 View Live

Considering ASGI support

@tomchristie wrote: I’m considering taking a proper crack at ASGI support, rather than just the proof-of-concept shim of #1265. I think you can pretty much keep API compatibility, except at some...

View Article



Image may be NSFW.
Clik here to view.

Considering ASGI support

@ahopkins wrote: I will jump in a little later with a more in depth response. But, after taking a look at this recently, my intention was to keep the internal server and also allow for ASGI...

View Article

Considering ASGI support

@sjsadowski wrote: I agree with not dropping current functionality in favor of ASGI functionality as a whole - there are always going to be slow adopters and compatibility issues, and of course those...

View Article

Image may be NSFW.
Clik here to view.

Considering ASGI support

@ahopkins wrote: tomchristie: Dropped the built-in server in favor of strictly decoupled-ness. As I said before, I am reluctant to do this. Having the built in server allows for Sanic to run with one...

View Article

Considering ASGI support

@tomchristie wrote: My preference would be to provide an alternative, something like calling app.asgi() instead of app.run() for functionality that implements the requirements. So I’m not sure how...

View Article


Image may be NSFW.
Clik here to view.

Considering ASGI support

@ahopkins wrote: tomchristie: I’m not personally particularly interested in adapting the Sanic sever part to deal with that, but if someone else took on that part on then great. Deal. @tomchristie You...

View Article

Image may be NSFW.
Clik here to view.

Considering ASGI support

@tomchristie wrote: Probably the biggest hurdle, and one that I am not sure will be avoidable, is how we handle websockets. So the good news on this front is that it looks like for most end-developers...

View Article

Considering ASGI support

@ahopkins wrote: @tomchristie I will follow your lead on this one, but if you need some help on this (especially on smoothing out the implementation of the non-ASGI stuff), I would be happy to join....

View Article


Considering ASGI support

@mungojam wrote: Any idea if any of the ASGI servers support Windows? I don’t see it explicitly mentioned on them and uvicorn seems to be based on gunicorn which doesn’t. That would be a big selling...

View Article


Considering ASGI support

@sjsadowski wrote: I think Daphne will run under a windows environment, but don’t hold me to that. Read full topic

View Article

Considering ASGI support

@tomchristie wrote: Uvicorn has windows support yup. (Tho if you were on Windows in production you’d need to use supervisor or circus for process management, rather than gunicorn with the uvicorn...

View Article

Considering ASGI support

@pgjones wrote: Hypercorn should work on windows as well (just not with the uvloop worker class). Read full topic

View Article

Image may be NSFW.
Clik here to view.

Considering ASGI support

@tomchristie wrote: Having taken a bit of a stab towards shoehorning ASGI support in without changing the existing API, it’s a pretty grim process. Acutally refactoring it out to ASGI itself would be...

View Article


Considering ASGI support

@ahopkins wrote: Okay … so I did some work on the test client with requests-async. Boiling it down, it does not look like we can switch our test client to only use it and replace aiohttp. Why? Because...

View Article

Image may be NSFW.
Clik here to view.

Considering ASGI support

@tomchristie wrote: ahopkins: Boiling it down, it does not look like we can switch our test client to only use it and replace aiohttp . Why? Because it does not support streaming requests. I can have...

View Article


Considering ASGI support

@tomchristie wrote: @ahopkins - Streaming requests and responses is now resolved in requests-async (See docs) Read full topic

View Article

Considering ASGI support

@ahopkins wrote: awesome! I think there is still another issue I need to dig into more. It seemed like h11 was complaining about having two Host headers set. I’ll resolve that and get a new client...

View Article


Considering ASGI support

@ahopkins wrote: Update: I have the test client and a working version of Sanic on ASGI. I’m working thru some tests (mainly test routes.py right now) using the ASGI interface. The question to...

View Article

Image may be NSFW.
Clik here to view.

Considering ASGI support

@tomchristie wrote: I have the test client and a working version of Sanic on ASGI. I’m working thru some tests (mainly test routes.py right now) using the ASGI interface. Nice work! Sorry I’ve not...

View Article

Considering ASGI support

@ahopkins wrote: I did want to talk with you about one item. I’m not at my computer so it’d be hard to explain fully without code. In short, the Sanic test client is setup to retrieve both the request...

View Article

Considering ASGI support

@ahopkins wrote: Opinions wanted… The new SanicTestClient uses requests-async instead of aiohttp. In the past, we got around having aiohttp be a hard dependency by doing the import right inside the...

View Article


Considering ASGI support

@ahopkins wrote: Read full topic

View Article


Considering ASGI support

@abuckenheimer wrote: a couple thoughts: on size: The actual size of the dependency isn’t that bad, I run most of my stuff ontop of a docker image (jfloff/alpine-python:3.7) and pip install...

View Article

Considering ASGI support

@tomchristie wrote: Worth keeping in mind too, that there’s still lots of work going on in the async HTTP client space that you’ll want to keep your eye on. The requests-async package is the minimal...

View Article
Browsing latest articles
Browse All 24 View Live




Latest Images