From: Harry Lewis (harryl@us.ibm.com)
Date: Wed Jan 10 2007 - 00:27:52 EST
Thanks, Ira.
----------------------------------------------
Harry Lewis
IBM STSM
Chairman - IEEE-ISTO Printer Working Group
http://www.pwg.org
IBM Printing Systems
http://www.ibm.com/printers
303-924-5337
----------------------------------------------
"McDonald, Ira" <imcdonald@sharplabs.com>
01/09/2007 11:26 AM
To
Harry Lewis/Boulder/IBM@IBMUS, "McDonald, Ira" <imcdonald@sharplabs.com>
cc
ps@pwg.org
Subject
RE: PS> REST version of PSI
Hi Harry,
Ah - obtaining status on existing jobs (which are probably nouns,
that is, named resources in a REST view) is a simpler problem.
If you don't need to cancel or otherwise modify those jobs then
a REST approach could be reasonable.
What PSI does very nicely is to model the Print Service and the
Print Device separately.
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Chair - FSG Open Printing Steering Committee
Blue Roof Music / High North Inc
PO Box 221 Grand Marais, MI 49839
phone: +1-906-494-2434
email: imcdonald@sharplabs.com
-----Original Message-----
From: Harry Lewis [mailto:harryl@us.ibm.com]
Sent: Monday, January 08, 2007 6:34 PM
To: McDonald, Ira
Cc: ps@pwg.org
Subject: RE: PS> REST version of PSI
Ira, thanks for your thoughts on REST/SOAP with PSI.
My main focus is on obtaining job status from a server that already has a
list of jobs and their state so I'm not really exercising PSI at it's
fullest
----------------------------------------------
Harry Lewis
IBM STSM
Chairman - IEEE-ISTO Printer Working Group
http://www.pwg.org
IBM Printing Systems
http://www.ibm.com/printers
303-924-5337
----------------------------------------------
"McDonald, Ira" <imcdonald@sharplabs.com>
01/08/2007 03:50 PM
To
Harry Lewis/Boulder/IBM@IBMUS, ps@pwg.org
cc
Subject
RE: PS> REST version of PSI
Hi Harry,
A quick few thoughts.
PSI is NOT at all SOAP-specific (the WSDL could easily
generate pure HTTP bindings), but PSI is RPC-style and
stateful (like all IETF, PWG, and vendor print protocols),
which is the exact opposite of REST.
From my reading of REST descriptions, it appears REST
is verb-poor and noun-rich and stateless. Neither PSI,
nor any other real print protocol is stateless - and I can't
imagine any easy transform to get there (or why you'd
want to).
Since there is consistency in available descriptions of
REST, designing RESTful applications seems to be a
statement in the eye of the beholder.
Would you care to expand on the reason for your
question?
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Chair - FSG Open Printing Steering Committee
Blue Roof Music / High North Inc
PO Box 221 Grand Marais, MI 49839
phone: +1-906-494-2434
email: imcdonald@sharplabs.com
-----Original Message-----
From: owner-ps@pwg.org [mailto:owner-ps@pwg.org]On Behalf Of Harry Lewis
Sent: Monday, January 08, 2007 1:15 PM
To: ps@pwg.org
Subject: PS> REST version of PSI
Is PSI so SOAP specific that a REST version would be out of the question?
What basic steps are needed to migrate PSI from SOAP to REST?
----------------------------------------------
Harry Lewis
IBM STSM
Chairman - IEEE-ISTO Printer Working Group
http://www.pwg.org
IBM Printing Systems
http://www.ibm.com/printers
303-924-5337
----------------------------------------------
-- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.432 / Virus Database: 268.16.7/620 - Release Date: 1/8/2007 4:12 PM-- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.432 / Virus Database: 268.16.8/621 - Release Date: 1/9/2007 1:37 PM
This archive was generated by hypermail 2.1.4 : Wed Jan 10 2007 - 00:28:08 EST