Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

split client, server & websocket stuff into separate packages #704

Closed
petri opened this issue Dec 23, 2015 · 2 comments
Closed

split client, server & websocket stuff into separate packages #704

petri opened this issue Dec 23, 2015 · 2 comments

Comments

@petri
Copy link

petri commented Dec 23, 2015

I wanted just an asyncio http client, and first tried aiohttp. However when installing, I saw the package is very large. I did not realize there is also websocket stuff etc.

It is of course ok to stay monolithic if aiohttp wants to become the Twisted of HTTP. But there are downsides.

It would be greate if there were separate client, server & websocket support packages.

@petri petri changed the title break client, server & websocket stuff into separate packages split client, server & websocket stuff into separate packages Dec 23, 2015
@asvetlov
Copy link
Member

Sorry, it will never happen.
That ship has sailed couple years ago.

@lock
Copy link

lock bot commented Oct 29, 2019

This thread has been automatically locked since there has not been
any recent activity after it was closed. Please open a new issue for
related bugs.

If you feel like there's important points made in this discussion,
please include those exceprts into that new issue.

@lock lock bot added the outdated label Oct 29, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Oct 29, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants