> Let me get this straight. A STEP.1 publisher would not need to
> implement the SENSE message format. Just the Text Event Protocol
> itself and this is designed to work with standard networking
> protocols. Right?
>> Can I ask, how would a STEP.1 publisher communicate with a SENSE
> server? Could it be via a telnet session? Is there a preferred
> method?
No, STEP.1 describes a protocol data format that is encapsulated in
the opaque data field of the SENSE message format. A property in
the encapsulating message would describe the data as a STEP.1 event.
A STEP.1 Publisher communicates with the SENSE Server using the Common
SENSE protocol, where STEP.1 is the format of the opaque data in the
event message. See FTP://ftp.pwg.org/pub/pwgsense/msgfmt.ps
Recall the Publication/Edition model of SENSE: A Publication
is registered to describe the printer; an Edition is registered
to represent the STEP.1 event stream. A STEP.1 Publisher then
issues events for that Edition. The SENSE Server then distributes
these events to interested Subscribers.
Initial registration of this Publication and Edition might be
handled by a STEP.1 Publisher embedded in the printer, or it might
be delegated to external software. If you wanted the printer
to work as automagically as possible, the embedded Publisher
would handle the registration as needed after determining the
appropriate SENSE domain and locating the SENSE Server.
Hmm, what we've been calling STEP.1 is called STEP.SingleLine.CC
in FTP://ftp.pwg.org/pub/pwg/sense/snsapx.htm#editions
/Jeff
---------------------------------------------------------------
Jeffrey D. Schnitzer | Email: jds at underscore.com
Underscore, Inc. | Voice: (603) 889-7000
41-C Sagamore Park Rd | Fax: (603) 889-2699
Hudson, NH 03051-4915 | Web: http://www.underscore.com
---------------------------------------------------------------