IPP Mail Archive: Re: RE: IPP> Last Call Comment: Job and Printer time attributes

Re: RE: IPP> Last Call Comment: Job and Printer time attributes

kugler@us.ibm.com
Tue, 27 Apr 1999 16:40:49 -0600

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: harryl@us.ibm.com: "RE: IPP> MOD - Issue 33 - proposed resolution to combining IPP/1."
Previous message: dcarney@us.ibm.com: "IPP> Updated comparison of job mib attributes with IPP attributes"

Original Article: http://www.egroups.com/list/ipp/?start=5655
> Carl,
> There are many ways to get a pretty good time value. From sniffing the
HTTP
> traffic to using a time server. Printers can have their time set via a
> console or web page. They could ask
> "http://tycho.usno.navy.mil/cgi-bin/timer.pl". they could use a GPS
> module...I hear they are getting pretty cheap.
> I do not believe requiring dateTime attributes will be an undue burden on
> printer implementations. It will be useful to IPP client applications.
> Pete
>

Pete-

None of those options sound appealing for really tiny embedded
applications. But you would know better than me about those! Anyway, I
was thinking... We can't count on HTTP requests carrying a Date header, but
we could require an IPP timestamp attribute on every request. Then a
really cheap Printer could get by with a simple clock (a tick counter)
rather than a Real Time Clock, and setting Printer time would be automatic.
Bonus is that IPP Printers wouldn't have to go on the Y2K inventory list.
And no batteries to replace.

-Carl

Next message: harryl@us.ibm.com: "RE: IPP> MOD - Issue 33 - proposed resolution to combining IPP/1."
Previous message: dcarney@us.ibm.com: "IPP> Updated comparison of job mib attributes with IPP attributes"