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

Allow persistent connection from subscriber to sender for SUBSCRIBE requests #22

Open
GoogleCodeExporter opened this issue Mar 13, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. The Documentation states that Growl for Windows v2.0 does not yet 
support socket reuse. 

What is the expected output? What do you see instead?
I am particular interested in a Subscribe mechanism, using the specified 
subscribe message and subscribe from a client to the growl server which 
then notifies via this already existing socket. So the client is able to 
be notified by the growl service even if the client is behind a NAT router.

What version of the product are you using? On what operating system?
growl-for-windows 2.01
Please provide any additional information below.

Original issue reported on code.google.com by [email protected] on 21 Dec 2009 at 12:20

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant