Hi,
I want to know the basics of the protocol before using the client
API, for that only i'm trying this. I already gain maximum, Instead of using
the GetMethod in API, before using that I'm interested to know what kind of
effort was taken by the developer who designs that API.
Actually when I first use Slide, when it creates a new folder in the
server namespace, I got exited and want to know how it is happening, now
things getting more and more interesting with DAV and its extensions. You
dont think the restrictions or missing facilities like so. I'm not that much
deeper with Slide. Just now only I start using client.
I already got the HttpCommons package code through ur mail
attachment. From that onwards Im looking into Client codes.
I run the same code with "webdav/Domain.xml" as it is in the webdav
folder, I found the same headers to be passed to the server what you passed
to it. And the response is not with multistatus, with 200 Ok. If you dont
mind, can you test this code with webdav of Tomcat server.
Its smart idea of creating xml body as you did, to avoid the space
usage. The reason I use the spaces are just to get the visual meaning full
on the screen. That is what u get in much prettier.
Thanx.
Vijay
=============== Outbound Message Headers =================
PROPPATCH /webdav/Domain.xml HTTP/1.1
Host: 192.168.0.5:8080
Connection: TE
TE: trailers, deflate, gzip, compress
Content-Type: text/xml
Content-Length: 142
=============== Outbound Message Body =================
<?xml version="1.0" ?><A:propertyupdate xmlns:A="DAV:"
xmlns:Z="DAV:"><A:set><A:
prop><Z:test>dirk</Z:test></A:prop></A:set></A:propertyupdate>
=============== Inbound Stream =================
HTTP/1.1 200 OK
Content-Length: 0
Date: Sat, 01 Sep 2001 12:15:40 GMT
Server: Apache Tomcat/4.0-b3 (HTTP/1.1 Connector)
----- Original Message -----
From: "Dirk Verbeeck" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, September 01, 2001 5:58 AM
Subject: Re: PROPATCH
> I have looked at your sample program and did some small modification to
> make it behave just like it is specified in the http RFC.
> - finish each header line with \r\n and an empty line between header and
> body.
> - remove spaces from xml (not really needed but is nicer for xml parser)
Its smart idea of creating xml body as you did, to avoid the space
usage. The reason I use the spaces are just to get the visual meaning full
on the screen. That is what u get in much prettier.
> I have run the program on tomcat 3 with slide deployed as webapp.
> Tomcat 4 should make no difference but test your installation with the
> slide client.
If you dont mind, can you test this code with webdav namespace in of
Tomcat server webapps.
> May I ask why you are not using the client API, is there some
> restriction or a feature that is missing, or are you just learning the
> protocol ?
I want to know the basics of the protocol before uising the client,
for that only i'm trying this. I already gain maximum, Instead of using the
GetMethod in API, before using that I'm interested to know what kind of
effort was taken by the developer who designs that API.
Actually when I first use Slide, when it creates a new folder in the
server namespace, I got exited and want to know how it is happening, now
things getting more and more interesting with DAV and its extensions. You
dont think the restrictions or missing facilities like so. I'm not that much
deeper with Slide. Just now only I start using client.
I already got the HttpCommons package code through ur mail
attachment. From that onwards Im looking into Client codes.
>
> Dirk
>
>
> =============== Outbound Message Headers =================
> PROPPATCH /slide/files/a HTTP/1.1
> Host: localhost:8080
> Connection: TE
> TE: trailers, deflate, gzip, compress
> Content-Type: text/xml
> Content-Length: 142
> =============== Outbound Message Body =================
> <?xml version="1.0" ?><A:propertyupdate xmlns:A="DAV:"
>
xmlns:Z="DAV:"><A:set><A:prop><Z:test>dirk</Z:test></A:prop></A:set></A:prop
ertyupdate>
>
> =============== Inbound Stream =================
> HTTP/1.0 207 Multi-Status
> Set-Cookie2: JSESSIONID=l3oi6f9g61;Version=1;Discard;Path="/slide"
> Set-Cookie: JSESSIONID=l3oi6f9g61;Path=/slide
> Servlet-Engine: Tomcat Web Server/3.2.2 (JSP 1.1; Servlet 2.2; Java
> 1.3.0; Windows 98 4.90 x86; java.vendor=Sun Microsystems Inc.)
>
> <?xml version="1.0" encoding="utf-8" ?><d:multistatus
>
xmlns:d="DAV"><d:response><d:href>/files/a</d:href><d:propstat><d:prop><Z:te
st
> xmlns:Z="DAV:"/></d:prop><d:status>HTTP/1.1 200
> OK</d:status></d:propstat></d:response></d:multistatus>
> =============== Inbound Stream Complete =================
Source.java
