Re: IPP> regarding "ipp:" (I spoke too soon...)

Robert Herriot <robert.herriot@Eng.Sun.COM> Fri, 03 July 1998 00:41 UTC

Delivery-Date: Thu, 02 Jul 1998 20:41:56 -0400
Return-Path: ipp-owner@pwg.org
Received: from cnri.reston.va.us (ns [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id UAA12139 for <ietf-archive@ietf.org>; Thu, 2 Jul 1998 20:41:55 -0400 (EDT)
Received: from lists.underscore.com (uscore-1.mv.com [199.125.85.30]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id UAA23937 for <ietf-archive@cnri.reston.va.us>; Thu, 2 Jul 1998 20:44:10 -0400 (EDT)
Received: from localhost (daemon@localhost) by lists.underscore.com (8.7.5/8.7.3) with SMTP id UAA15178 for <ietf-archive@cnri.reston.va.us>; Thu, 2 Jul 1998 20:41:46 -0400 (EDT)
Received: by pwg.org (bulk_mailer v1.5); Thu, 2 Jul 1998 20:37:29 -0400
Received: (from daemon@localhost) by lists.underscore.com (8.7.5/8.7.3) id UAA14550 for ipp-outgoing; Thu, 2 Jul 1998 20:32:15 -0400 (EDT)
Message-Id: <199807030027.RAA06076@woden.eng.sun.com>
X-Sender: rherriot@woden.eng.sun.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1
Date: Thu, 02 Jul 1998 17:32:49 -0700
To: Keith Moore <moore@cs.utk.edu>, "Scott Isaacson" <SISAACSON@novell.com>
From: Robert Herriot <robert.herriot@Eng.Sun.COM>
Subject: Re: IPP> regarding "ipp:" (I spoke too soon...)
Cc: moore@cs.utk.edu, paulmo@microsoft.com, ipp@pwg.org
In-Reply-To: <199807022308.TAA12793@spot.cs.utk.edu>
References: <Your message of "Thu, 02 Jul 1998 15:19:20 MDT." <s59ba512.033@novell.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; types="text/plain,text/html"; boundary="=====================_793776380==_.ALT"
Sender: owner-ipp@pwg.org

Keith,

SWAP (http://people.netscape.com/kswenson/SWAP/charter.html )
is a project with much similarity to IPP.  

It uses HTTP, but has special methods and encodes its parameters in XML.
It is for workflow management, but it has a set of operations that are 
rather similar to IPP (see below).  The SWAP web page list you, Keith Moore, 
as one of the area directors.

The following text comes from the SWAP charter:

   "The purpose of working group is to provide a simple HTTP based way to 
   invoke, monitor, control, and be informed about a generic asynchronous 
   service. 

   The protocol defines: 

        ·       a standard way to invoke a generic service, which returns an
instance ID 

   Then, using the ID, the protocol defines how to 

        ·       get the current status of that instance of the service, 
        ·       give that instance of the service data values 
        ·       pause or resume that instance of the service 
        ·       retrieve preliminary results of that instance of the service 
        ·       register an address to receive event notifications from the
service 
        ·       receive events from that instance of the service "

What are your thoughts about SWAP?  Are they going to be allowed to 
use an http scheme? 

Bob Herriot