Similarities and Differences between SWAP and IPP
draft-swenson-swap-vs-ipp-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Thomas N. Hastings , Keith D. Swenson | ||
| Last updated | 1998-08-06 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
https://www.ietf.org/archive/id/draft-swenson-swap-vs-ipp-00.txt
Abstract
IPP (Internet Printing Protocol) has been compared in conversations to SWAP (Simple Workflow Access Protocol). Both are for starting an asynchronous job, and then being able to check up on it later. The IPP is specifically designed for printers and print jobs. SWAP is more generic, and is generally oriented toward more computational jobs. But many of the problems encountered are the same, and the approach to the solutions can be examined and compared. This document goes through the features point by point and shows in what ways they are similar, and more importantly in what ways their approaches differ. The purpose of this is to guide discussions about the two protocols.
Authors
Thomas N. Hastings
Keith D. Swenson
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)