| Summary: | [presence][api][plan] History API implementation | ||
|---|---|---|---|
| Product: | [RT] ECF | Reporter: | Danila Ermakov <danila.ermakov> |
| Component: | ecf.core | Assignee: | Danila Ermakov <danila.ermakov> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | danila.ermakov, remy.suen, slewis |
| Version: | 1.0.2 | Keywords: | helpwanted, plan |
| Target Milestone: | 1.1.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | 177014, 177016 | ||
| Bug Blocks: | |||
|
Description
Danila Ermakov
(In reply to comment #0) > Implementation details: > 1. Persistance - directory tree with root configured from plugin preferences - > local_user_id/remote_user_id. Content - XML/UTF8 (possibly not-valid XML - > without root element - to improve performance on big history files) Seems reasonable...I would like to keep the requirements to a minimum...i.e. just use existing preferences service. > 2. encryption? > At this time, I would say 'no'. Moving target milestone to 2.0.0M4. Danila, is there some chance of reviving this work for ECF 3.0/Galileo release? Thanks! Given change in project emphasis (to OSGi Remote Services) and away from present/IM apis, as well as limited project resources (committer time), it now seems unlikely that this will be addressed. If resources become available I would be happy to see this happen...so please reopen if possible. |