RE: keepalive in socket server program

Seems to me a simple RESTful web service call might be a better vehicle for this, but I don't know your vendors technical abilities.

Your programming then becomes dead-simple rather than writing a socket server app.

Not that socket servers are hard, but why in today's world of web services :-)

Regards,

Richard Schoen | Director of Document Management Technologies, HelpSystems
T: + 1 952-486-6802
RJS Software Systems | A Division of HelpSystems
richard.schoen@xxxxxxxxxxxxxxx
www.rjssoftware.com
Visit me on: Twitter | LinkedIn

------------------------------

message: 6
date: Mon, 31 Aug 2015 09:34:59 -0400
from: Jeff Young <jyoung0950@xxxxxxxxx>
subject: Re: keepalive in socket server program

Alan, Nathan, Richard & Scott,
Thank you for the information.
At this time, there is only going to be one client.
I am going to use a single server job to receive the data and send it to a data queue for processing.
At some point, the data queue method may be to slow for the volume of data being received and I will have to look into another method.
The project that I am working on involves another software vendor, and they are defining the interface specifications and requirements.
I will check with them as to exactly they will send as a keepalive and what they want back.
As always, the information that I receive here in answer to my questions has greatly improved my knowledge.

Thank you all for you help.


Jeff Young
Sr. Programmer Analyst