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

Suggestion: keep connection alive #175

Open
controversial opened this issue Mar 24, 2016 · 2 comments
Open

Suggestion: keep connection alive #175

controversial opened this issue Mar 24, 2016 · 2 comments

Comments

@controversial
Copy link

I have no idea if this is still being actively developed. I kind of assume it's not, since @sveale's last contribution was Feb 22. Anyway, I was wondering if it'd be possible to implement a mechanism by which connections aren't closed so quickly. If I want to open multiple remote files all at once, remote-edit has to reconnect every time, which is sometimes slow. Would it be possible to keep connections alive longer, just for convenience? Maybe the connection to the server could be automatically closed after something like 5 minutes?

@sveale
Copy link
Owner

sveale commented Mar 24, 2016

Hi 😊. It's still being maintained, but I don't have that much time nor do I use the plugin myself anymore. You're more than welcome to submit a PR. Sounds like a good idea. Maybe adding an option so the user can specify the time?

Den 24. mar. 2016 kl. 21.24 skrev Luke Deen Taylor notifications@github.com:

I have no idea if this is still being actively developed. I kind of assume it's not, since @sveale's last contribution was Feb 22. Anyway, I was wondering if it'd be possible to implement a mechanism by which connections aren't closed so quickly. If I want to open multiple remote files all at once, remote-edit has to reconnect every time, which is sometimes slow. Would it be possible to keep connections alive longer, just for convenience? Maybe the connection to the server could be automatically closed after something like 5 minutes?


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

@controversial
Copy link
Author

I'll try. I haven't looked at the code for this all, but I'll see what I
can do. I'm familiar with but not great at JavaScript, but I have no
experience with CoffeeScript, and know next to nothing about Atom's package
system.

That said, if it's an easy fix modifying existing code I might be able to
scrape something together with a little googling.

You say you no longer use this package. Is this because you no longer do
remote editing with Atom, or have you found another solution? If it's the
latter, I'd love to hear it.
On Thu, Mar 24, 2016 at 4:30 PM Sverre Aleksandersen <
notifications@github.com> wrote:

Hi 😊. It's still being maintained, but I don't have that much time nor do
I use the plugin myself anymore. You're more than welcome to submit a PR.
Sounds like a good idea. Maybe adding an option so the user can specify the
time?

Den 24. mar. 2016 kl. 21.24 skrev Luke Deen Taylor <
notifications@github.com>:

I have no idea if this is still being actively developed. I kind of
assume it's not, since @sveale's last contribution was Feb 22. Anyway, I
was wondering if it'd be possible to implement a mechanism by which
connections aren't closed so quickly. If I want to open multiple remote
files all at once, remote-edit has to reconnect every time, which is
sometimes slow. Would it be possible to keep connections alive longer, just
for convenience? Maybe the connection to the server could be automatically
closed after something like 5 minutes?


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#175 (comment)

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

2 participants