> We need one of the components in our product to be
> able to access Slide via regular HTTP. If I understand it
> right then a simple HTTP GET (with proper authentication)
> should do it.
Well you have to cache the contents somewhere. That
may either be done by some sort of http-proxy or
on the client-side. Anyway that's nothing that the
slide server can do for you. All it does is to set
the Last-Modified value in the header. The client
would have to cancel the request in case the header
date is the same as the one he cached or something.
Alternatively you may consider calling a HEAD,
evaluate the header and then call a GET or use the
cached version instead. If your client handles
304 Not Modified the right way then you should be
fine.
> But it is very important for us (performance wise) to be able
> to avoid re-getting the file if it wasn't modified
> since the previous fetch.
>
> In HTTP there is an "If-Modified-Since" modifier to GET requests,
> would Slide function as expected for such a request? If not then
> what would be the simplest way to achieve the same effect? Will
From taking a quick look at the code I would say that
it returns a 304. If that's what you expect...
Otherwise, I would suggest to do it on the client side.
Call a HEAD, read the modified flags, call GET in case
that's necessary.
> we have to resort to a full-fledged WebDAV client? (this particular
> component is written in C++, so we can't use Slide's client code).
I have successfully used libwww 5.4.0
( http://www.w3.org/Library ) to connect to slide.
Alternatively you may also use neon
( http://www.webdav.org/neon/ ).
libwww is under some apache-like license and well
documented.
l8r...
Thomas
--
Thomas Sch�ppel, bit~side GmbH Fon: +49+30+394054-28
Salzufer 14a, 10587 Berlin Fax: +49+30+394054-50
http://www.bit-side.com Email: [EMAIL PROTECTED]
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
