Skip to content
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

no support for properties that are not plain XML-safe character strings (binary data, XML nodes) #71

Open
GoogleCodeExporter opened this issue Apr 28, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

Forwarded from http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710697


Dear Maintainer,

there's currently no way to return property values from
dav_interface.get_prop() that are anything else than plain characters
strings with no XML-unsafe characters. While
PROPFIND.mk_prop_response() would accept a xml.dom.minidom.Element or
even a list list of those, the Element can only be created from inside
mk_prop_response(): the xml.dom.minidom implementation requires the
Document object for instantiating Nodes, but
PROPFIND.mk_prop_response() and PROPFIND.get_propvalues() do not pass
the Document object down to dav_interface.get_prop().

I'm not sure what the best way to add support for non-string property
values would be. Passing the Document as another parameter to
get_prop() would break existing code using pywebdav. Maybe introducing
a new method get_prop2() and falling back to the one? If the check is
done outside the loop, it may be reasonably efficient.

Original issue reported on code.google.com by [email protected] on 1 Jun 2013 at 5:25

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant