| Summary: | [client] Look at using plugins for File Service | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Simon Kaegi <simon_kaegi> | ||||
| Component: | Client | Assignee: | John Arthorne <john.arthorne> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P3 | CC: | malgorzata.tomczyk, mamacdon, simon_kaegi | ||||
| Version: | 0.2 | ||||||
| Target Milestone: | 0.2 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Simon Kaegi
Created attachment 188820 [details]
Work in progress
I have made some progress, but things are broken in the current state so I don't want to commit it. Simon feel free to take a look. Basically I wanted to get fileClient.js to work in both the plugin use case, and in the old case where the file service was registered manually by the various pages.
File Service and User Service should be hosted on the same site. I raised a bug for using plug-ins for User Service too. (In reply to comment #2) > File Service and User Service should be hosted on the same site. I raised a bug > for using plug-ins for User Service too. See Bug 337104. What are you planning to do with all the callback functions that are normally send to the file service? "updateFunction", "onCreate", "onLoad" etc? We can't pass functions as arguments to services provided by plugin. The individual service calls return a "then-able promise". The Serviceregistry also lets service providers fire events and consumers register for those events. This work has been released. There will be some follow-on work in M7 related to authorization for the file plugin, and for supporting more than one file plugin installed at once. |