| Summary: | Implement export service | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | John Arthorne <john.arthorne> |
| Component: | Client | Assignee: | John Arthorne <john.arthorne> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 0.2 | ||
| Target Milestone: | 0.2 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 334698 | ||
|
Description
John Arthorne
I have implemented an export service. Each file/directory has a new link on the JSON object called "ExportLocation". Performing a GET on that URL will download a zipped representation of that file/directory (recursively). We can get into further options if necessary, but this provides a simple starting point. Even better, the client side should be trivial to write - just expose the export link somewhere, and the browser's download manager should take care of the rest.
Example:
GET /file/C?depth=1
{
"Children": [...],
"ChildrenLocation": "http://localhost:8080/file/C?depth=1",
"Directory": true,
"ExportLocation": "http://localhost:8080/xfer/export/C.zip",
"ImportLocation": "http://localhost:8080/xfer/C",
...
}
Exporting this project is performed via:
GET http://localhost:8080/xfer/export/C.zip
(In reply to comment #1) > Even > better, the client side should be trivial to write - just expose the export > link somewhere, and the browser's download manager should take care of the > rest. Sweet and simple! I added a download link in the UI. Marking fixed. |