Closed Bug 443931 Opened 16 years ago Closed 14 years ago

Weave sharing API should conform to conventions of registration API

Categories

(Cloud Services Graveyard :: Server: Sync, defect)

Product:
Cloud Services Graveyard
Component:
Server: Sync
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID
Milestone:
Future

People

(Reporter: avarma, Assigned: telliott)

References

(
URL
)

Details

Currently, Weave's sharing API doesn't conform at all to the conventions of the registration API, which itself are much more consistent with standard RESTful APIs; see the URL, which is a snapshot of the wiki documentation page, for more details.
We'll likely want to revisit the sharing API when we add it back, on top of the new server.  Setting to future.
Target Milestone: -- → Future
Component: Weave → General
Product: Mozilla Labs → Weave
QA Contact: weave → general
Assignee: nobody → telliott
Component: General → Server
QA Contact: general → server
We don't have this yet, and when we do it'll look all nice and RESTy
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.