Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

ECF Conference Call 12.10.2008

Revision as of 07:58, 7 December 2008 by Unnamed Poltroon (Talk) (Agenda: We need bundles names for the resource synchronization bundle names and we need to refactor the examples plug-in.)

Attendees

Agenda

Resource Synchronization between N Workspaces

There are two similar but different functionalities:

  1. bug 239048 - keep N resources synchronized by distributing changes made to one resource to N-1 other peers
  2. bug 257017 - synchronize a resource with the same resource elsewhere using Compare and Team APIs

Remy has working code written but the bundles' names need to be finalized before they are committed to CVS.

Presence API implementation on top of org.eclipse.ecf.example.collab

Time has shown that people who install the ECF examples and connect around with the ecftcp protocol appears to assume that features implemented over the Datashare APIs (like DocShare) should work for them (see this blog post and this newsgroup post). This is false but is quite misleading as there are often features in the examples plug-in which kind of works but are similar in name to the actual feature that's been pushed down to ECF core. More often than not, the core feature could've been reused by the examples plug-in but it doesn't work because the examples plug-in doesn't offer an implementation of the Presence API. Unfortunately, since a chat window appears, it adds to the false impression that the examples plug-in gives to the user.

Since the plug-in is an "example", we should essentially be allowed to add, change, and delete things at will. Requesting comments from Scott as to the implications of such drastic actions.

Back to the top