[Asterisk-Dev] Open source time card application for Asterisk

Tilghman Lesher tilghman at mail.jeffandtilghman.com
Tue Sep 27 08:26:06 MST 2005


On Tuesday 27 September 2005 08:27, Steven wrote:
> Small problem, this gives you no ability to log a clock out if you
> missed the clock in.

I'd consider that a feature.  Most timeclocks don't.

> Also I don't know enough about the ODBC functions, but does it give
> you any feedback on failure?

No, it doesn't.

> On suggestion to act more like a time clock would be to merge them
> together into one function that just recorded a clock event. Then you
> use knowledge about the time and ordering of events to determine if
> it is a clock in or clock out event.

That's certainly another way to do it.  I prefer to have events matched.

> If the two are merged, and a clock in event failed or, more likely,
> missed by the user, a clock out event can still be processed and
> later corrected by inserting a value that the administrator is
> willing to accept as a clock in event.

In other words, the record is fudged.  If that's the case, the admin
can certainly fudge the entire record just as easily.

-- 
Tilghman



More information about the asterisk-dev mailing list