Re: Sockets and Time Clocks?

[Scott Klement <klemscot@xxxxxxxxxxxx>]

>
> But I'm new to sockets and kind of lost on the "Time Clock as Client"?
>

Everything has a protocol that it speaks.  You have to learn that protocol
to know what is required to implement this.

I am not aware of any RFCs that document a standard protocol for Time
Clocks....  There may be one, but I haven't yet run across it.

Therefore, you'll have to find out from the company that's selling you the
clocks and/or company that makes the clocks exactly how they talk to their
server.  If there is no standard, it seems unlikely that every clock
on the market would use the same protocol, so you'll want to get
information for your specific model from the people who are selling it to
you, or from the manufacturer.   Should just be a TCP or UDP connection,
where messages are sent indicating each "punch", and you have to respond
in the correct way.

Once you're armed with that kind of information, the rest shouldn't be so
difficult :)

My hunch would be that they'd send UDP packets containing a time stamp and
some employee ID number, and probably expect a packet back acknowledging
it.   I can't think of a reason they'd want to make it any more
complicated than that...   and using TCP would seem silly for something
this small -- but that's just a hunch.

> Tips,Comments, and/or knock in head always accepted.

I'm interested in hearing how this turns out...   :)