Harry,
That is one mode, but I would not say that it is the main mode since it is an optional operation. We have agreed that SOAP can use either SMTP or HTTP. The SetSchedule operation (to my mind) make sense primarily in an entirely email oriented implementation.
In many cases, MFPs are not managed by the IP group and an easy, non-IT dependent mode of operation is desirable. Having to set up a mail account for every printer is a bother (although this can be reduced by using a proxy). Using the basic terminal web access is generally easier and involves less people in an organization.
Of course, if you want to implement an SNMP based protocol, that's fine. But the SetSchedule operation is optional.
For either binding, the remote management is enabled by the RegisterforMnagement operation.
Bill Wagner
-----Original Message-----
From: Harry Lewis [mailto:harryl at us.ibm.com]
Sent: Monday, May 03, 2004 1:36 P
To: wbmm at pwg.org
Subject: WBMM> Setting the Schedule
I want to reaffirm that the (main) mode we are anticipating for getting a schedule set in a managed entity is for the Manager, using SMTP, to send a SetSchedule operation which includes a UpdateSchedule Action in the Schedule... whereby the Agent will perform a GetSchedule.
----------------------------------------------
Harry Lewis
Chairman - IEEE-ISTO Printer Working Group
http://www.pwg.org
IBM Printing Systems
http://www.ibm.com/printers
303-924-5337
----------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.pwg.org/archives/wims/attachments/20040503/3073a1a9/attachment.html