Open GoogleCodeExporter opened 9 years ago
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 briandun...@gmail.com
on 17 Jun 2010 at 4:20
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 briandun...@gmail.com
on 9 Oct 2011 at 9:01
Original issue reported on code.google.com by
t0bit0b...@gmail.com
on 21 Dec 2009 at 12:20