Skip to content
This repository was archived by the owner on Jun 5, 2024. It is now read-only.
This repository was archived by the owner on Jun 5, 2024. It is now read-only.

Dav response parser & possible usage of existing dav libraries #1036

@lookacat

Description

@lookacat

With the work on https://jira.owncloud.com/browse/WEB-1095 we have found some issues regarding our dav.js.

  1. Parsing of e.g. Propfind response does manipulate the keys und values of a prop significantly. This lead to information being thrown away. Only limited value types are supported and more complex values are either parsed wrong or are just cut off. It's also really time consuming to extend the parsing logic, and it's hard to understand existing code. E.g _parsePropNode in dav.js is not providing much value and is really hard to extend.

  2. We've discussed why we did write our own dav client if there are some promising libraries out there that are well maintained and would save us time and effort. Libraries we came across are:

  1. We should consider switching to an external library but we need to make sure they suit our needs and fit in with our code.

Issues that will be resolved by this:
#1032

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions