- From: <kswenson@ms2.com>
- Date: Wed, 2 Dec 1998 13:49:08 -0800
- To: rheim@crusher.jcals.csc.com, gbolcer@endeavors.org
- Cc: ietf-swap@w3.org
The method is specified as part of the HTTP protocol. It is actually the first characters of the first line of the header of the request. Most requests to a web server use the GET method, so the browser will send as the first line to the server something like: GET /pub/doc/index.html HTTP/1.1 For this reason the method does not need to be part of the XML body of the message. We were fairly well persuaded by ietf members who worked on WebDAV that this was the right way to extend the HTTP protocol for use in things like SWAP. By the way, the WebDAV spec goes into detail about the PROPFIND method you used as an example. -Keith > -----Original Message----- > From: Richard Heim [mailto:rheim@crusher.jcals.csc.com] > Sent: Wednesday, December 02, 1998 12:17 PM > To: Gregory Alan Bolcer > Cc: SWAP LIST > Subject: RE: SWAP Example > > > > Question: > doesn't this need a METHOD name after the > <d:observer> tag? > something like: > > <d:observer>http://www.ics.uci.edu/pub/ietf/swap/chair.html</d > :observer> > <d:method>PROPFIND</d:method> > > Actually - I thought it would look more like > this (sorry - > no namespaces :( ): > > <SWAP> > <INTERFACE>PROCESSINSTANCE</INTERFACE> <-- > PROCESSINSTANCE is > a value - not a tag????? > <METHOD>PROPFIND</METHOD> <-- the > PROCESSINSTANCE method as a METHOD tag value > <KEY>http://rheim.jcals.csc.com</KEY> > <--- > the URL goes in the key field > <VALIDSTATES> > <li>open.notRunning</li> > <li>open.running</li> > </VALIDSTATES> > <STATE>open.notRunning</STATE> > <DATA> > <city>San Francisco<city> > <state>California<state> > </DATA> > </SWAP> > > Otherwise - how do we know which method is > being requested? > > thanks, > rich > > > > ************************************************************** > ************** > ******************************************************************* > > >>Request > > CREATEPROCESSINSTANCE /submit/order?proc=10 HTTP/1.1 > > Host: www.widget-makers.com > > Content-Type: text/xml > > Content-Length: xxxx > > Authorization: Digest username="skreddy" > > realm="skreddy@oracle.com", ... > > > > <?xml version="1.0" ?> > > <?xml:namespace ns="SWAP:" prefix="d" ?> > > <?xml:namespace ns="http://conf.pcmanufact.com/" > prefix="z" > > ?> > > > > <d:swap> > > > > > <d:observer>http://www.ics.uci.edu/pub/ietf/swap/chair.html</d > :observer> > > > > <d:name>equipment-purchase-process</d:name> > > <d:subject>procurement</d:subject> > > <d:description>New equipment purchase</d:description> > > <d:contextData> > > <z:processor>pentiumII</z:processor> > > <z:memory> > > <z:size>256 Meg</z:size> > > <z:speed>60 ns</z:speed> > > <z:type>DRAM</z:type> > > </z:memory> > > <!-- "name, billing address, etc." --> > > </d:contextData> > > <d:startImmediately>no</d:startImmediately><!-- > "available?" > > --> > > > > </d:swap> > > > > >>Response > > HTTP/1.1 207 Multi-Status > > Content-Type: text/xml > > Content-Length: xxxxx > > > > <?xml version="1.0" ?> > > <?xml:namespace ns="SWAP:" prefix="d" ?> > > <?xml:namespace ns="http://conf.pcmanufact.com/" > prefix="z" > > ?> > > > > <d:multistatus> > > <d:response> > > <d:processInstance> > > > > <d:href>http://www.widget-makers.com/status?proc=10.1 > > </d:href> > > <?-- "other items as defined by > process" --> > > </d:processInstance> > > <d:propstat> > > <d:prop><z:size/></d:prop> > > <d:status>HTTP/1.1 409 > Conflict</d:status> > > <d:comment>part unavailable</d:comment> > > </d:propstat> > > <d: propstat> > > <?-- "other resource properties" --> > > </d:propstat> > > </d:response> > > </d:multistatus> >
Received on Wednesday, 2 December 1998 16:48:08 UTC