-
Notifications
You must be signed in to change notification settings - Fork 159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What clients has jsDAV been tested against? #6
Comments
This is not really an issue, now is it? ;-) But your friend is right! No WebDAV client is alike... however, since jsDAV is a more-or-less port from SabreDav (http://code.google.com/p/sabredav/), you may assume that it works on the same clients they tested their PHP project against. There is a catch though: I haven't been able yet to port all the features from SabreDAV to jsDAV yet. But they will be there soon, as well as CalDAV support. |
Mike, you dropped by the Node list discussion of jsDAV and answered some questions a while ago. I then posted some followups: https://groups.google.com/group/nodejs/browse_thread/thread/1662644ee80527ba/6c55f74e7bc303b7 Also I do think your docs ought to include a list of clients (with versions) it's been tested against... |
is there any node.js module that can talk to jsDAV (read and write) ? the one i did look at either didnt work out-of-the-box or are missing a lot of documentation (like a simple working - list calendars/events of user etc) |
I'm curious as to what WebDAV clients (and versions of them) this module has been tested against?
An experienced developer who's tried to make WebDAV work just told me that "the intersection where all webdav clients out there work the same is virtually null."
The text was updated successfully, but these errors were encountered: