Ted Dunning wrote:
> But the rest or dav layer is still *really* handy if only for debugging and
> inspecting what new programs are doing.
Agreed; I wrote mod_shmap for those purposes in the httpd world.
I've got some ideas for a mod_zookeeper that would permit other
modules to take advant
It is absolutely hard to imagine how to deal with these.
But the rest or dav layer is still *really* handy if only for debugging and
inspecting what new programs are doing.
Another dav servlet approach is found here:
http://could.it/main/a-simple-approach-to-webdav.html
I have had very good re
Andrew Kornev wrote:
> Zookeeper handle is thread-safe. The recommended approach is to share a
> single zookeeper zhandle between application threads. Unless, of course,
> you'd like to connect to multiple zookeeper clusters (quorums) from the same
> application in which case you'd have to have a
Patrick Hunt wrote:
> Have you heard anyone implementing webdav on top of zookeeper? Seems
> like it would be a pretty good match (my experience with webdav is
> limited though). There are lots of webdav clients and client libs available.
I know from experience with httpd that it is possible
