Opened 11 years ago

Closed 7 years ago

#2196 enhancement closed wontfix (wontfix)

Need a generic API for reading and writing resource contents

Reported by: Wilfredo Sánchez Vega Owned by:
Priority: high Milestone: Web2-Gold-Master
Component: web2.dav Keywords:
Cc: Wilfredo Sánchez Vega Branch:
Author:

Description

Need a generic API for reading and writing resource contents so that we can, for example, copy one DAV resource to another without having to know anything about the underlying implementation.

We have such a mechanism for properties, but not for the resource content.

The API (at least the read side) may be appropriate for non-DAV resources.

GET could (should?) be implemented on top of the read API.

Change History (6)

comment:1 Changed 11 years ago by Wilfredo Sánchez Vega

Milestone: Web2-Gold-Master
Priority: normalhigh
Status: newassigned

comment:2 Changed 11 years ago by Jean-Paul Calderone

I'm sure there are good reasons IConsumer/IProducer is insufficient. Could you include them on this ticket? They may help inform the design of a superior replacement.

comment:3 Changed 11 years ago by Wilfredo Sánchez Vega

Well, having never claimed that IConsumer/IProducer is insufficient (or heard of them); no, I can't.  Perhaps you could, since you are sure that there are good reasons.

My goal in this ticket is to add methods to DAVResource, which are presently lacking, which provide a read/write API.  I'll look at IConsumer/IProducer and see if they fit (or why they don't).

comment:4 Changed 11 years ago by Wilfredo Sánchez Vega

I'm not really seeing how IProducer and IConsumer will help me here. IStream is more in line with what web2 does, and probably fits well.

comment:5 Changed 7 years ago by <automation>

Owner: Wilfredo Sánchez Vega deleted

comment:6 Changed 7 years ago by washort

Resolution: wontfix
Status: assignedclosed
Note: See TracTickets for help on using tickets.