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

switch to sockets api #19

Open
lanterndev opened this issue Sep 26, 2013 · 0 comments
Open

switch to sockets api #19

lanterndev opened this issue Sep 26, 2013 · 0 comments

Comments

@lanterndev
Copy link
Contributor

App Engine released a sockets API back in April 2013. Currently still in Preview and still only available to paid apps (as of March 2014).

The sockets API could allow HTTP CONNECT support as well as streaming the response to the client without storing it in memory first.

If the sockets API is ever made available to free apps as well as paid apps, we could make it super easy for censored users to create their own laeproxy instances, which would add a lot more capacity to the network. Some censored users might even be willing and able to pay for their own laeproxy instances in the meantime, so a first pass could just be writing up some docs on how to deploy your own instance, and then make it easy to tell lantern to use it.

Would obsolete #3, #4, #5, and #10.

@lanterndev lanterndev changed the title switch to sockets api? switch to sockets api Mar 18, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant