Allow persistent connection from subscriber to sender for SUBSCRIBE requests

[GoogleCodeExporter]

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

[GoogleCodeExporter]

socket re-use only applies to the machine that initially makes the connection. 
this means that multiple REGISTER and NOTIFY requests could be sent by the 
sender on the same socket without opening a new one each time.

for SUBSCRIBE requests, they originate from what is essentially the receiver. 
the connection is closed and later, when the sender has notifications to send, 
they forward the REGISTER or NOTIFY requests as appropriate. in theory, the 
sender (in this case, the machine that has been subscribed to) could reuse its 
socket for forwarding multiple notifications (if socket re-use were 
implemented), but that is all.

that said, i do understand the scenario you describe and see the use case for 
it. i wont mark this issue closed, but i am going to change it to a feature 
request since it is new functionality.

Original comment by [email protected] on 17 Jun 2010 at 4:20

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

changed the title from 'Growl for Windows v2.0 does not yet support socket 
reuse. ' to 'Allow persistent connection from subscriber to sender for 
SUBSCRIBE requests' to avoid confusion

Original comment by [email protected] on 9 Oct 2011 at 9:01

• Changed title: Allow persistent connection from subscriber to sender for SUBSCRIBE requests