[
https://jira.nuxeo.org/browse/NXP-5053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=76163#action_76163
]
Florent Guillaume commented on NXP-5053:
----------------------------------------
In the current code the URLs for remoting have the following form.
For the Mapper, it's a POST to http://localhost:8181/nuxeo/vcs containing
serialized information, and returning serialized information.
For the BinaryManager, the HTTP API implemented by BinaryManagerClient /
BinaryManagerServer is:
- GET http://localhost:8181/nuxeo/binary?digest=...
to get a given digest, returns 200, or 404 if not present.
- POST http://localhost:8181/nuxeo/binary?digest=...
to put a file, which must have Content-Type application/octet-stream. The
digest is here to double-check the transfer. Returns 201 (Created) if ok, 409
(Conflict) if digests don't match.
> VCS backend proxying to a remote VCS
> ------------------------------------
>
> Key: NXP-5053
> URL: https://jira.nuxeo.org/browse/NXP-5053
> Project: Nuxeo Enterprise Platform
> Issue Type: New Feature
> Components: Core SQL Storage
> Reporter: Florent Guillaume
> Assignee: Florent Guillaume
> Priority: Major
> Fix For: 5.3.2
>
>
> This feature will make it possible to run a Nuxeo with the backend store not
> in SQL but in a remote VCS on another machine. The remote VCS will therefore
> be a kind of "proxy" to the final SQL database.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
