Hi Mark, I suggest you to take a look at the ZeroMQ Guide book and search for "slow joiner" issue... there are a few patterns to fight against that issue...
HTH Francesco 2017-12-08 21:01 GMT+01:00 Mark Holbrook <[email protected]>: > Hi all, > > > > We are going to be writing a Windows Service app which will hopefully > listen for incoming data from our main application and write it to a > database then to the cloud. > > > > I’m struggling with one basic understanding problem on how to do this… > > > > The Windows Service app will likely startup well before our application > will. It needs to go into “listening” mode. > > > > When our app starts it needs to connect to the service and start sending > it data. > > > > All seems logical but in my tests using a PULL socket as the service and a > PUSH in our app if I start the service before the app they do not connect. > I have to start the push socket first then the pull. Which is backwards of > what we need. > > > > I also cannot see how I can tell in my app if connection to the service is > successful. The connect methods on the C# CLR Nuget offer no return > indicating success or failure. > > > > So my question is: > > > > What pattern would allow the receiver to sit and listen and have the > sender connect later and start sending. We also need to support the case > of the sender disconnecting and terminating then being restarted and > reconnecting. > > > > Is there some way to know that a connection has successfully been made or > is that usually done by like a REQ response thing? > > > > Thanks in advance! > > > ************************************************************ > **************************************** > This message contains information that may be privileged or confidential > and is the property of Propel Labs, Inc. It is intended only for the person > to whom it is addressed. If you are not the intended recipient, you are not > authorized to read, print, retain, copy, disseminate, distribute or use > this message or any part thereof. If you receive this message in error, > please notify the sender immediately and delete all copies of this message. > ************************************************************ > **************************************** > > _______________________________________________ > zeromq-dev mailing list > [email protected] > https://lists.zeromq.org/mailman/listinfo/zeromq-dev > >
_______________________________________________ zeromq-dev mailing list [email protected] https://lists.zeromq.org/mailman/listinfo/zeromq-dev
