[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[dsdp-tm-dev] FW: structuring projects and RSE function
|
Finally,
a more recent E-Mail regarding availability of the ECF Fileshare
API in the latest ECF snapshot.
Cheers,
Martin
--
Martin Oberhuber - WindRiver, Austria
+43(662)457915-85
-----Original Message-----
From: Scott Lewis [mailto:slewis@xxxxxxxxxxxxx]
Sent: Sunday, February 05, 2006 2:19 AM
To: Oberhuber, Martin
Cc: David Dykstal; Scharf, Michael
Subject: Re: FW: structuring projects and RSE function
Hi Martin and David,
Renewed greetings to all three Martin, David, and Michael. I hope all
is well.
David I was wondering if there was any further word on RSE
availability? I would like to implement an ECF provider on RSE. Since
we corresponded previously we've completed providers based upon
zeroconf/bonjour (discovery), Java Message Service, IRC (chat), Yahoo
(IM/chat) and Sametime (IM/chat).
Also, FYI ECF 0.6.2 includes a new 'fileshare' API for asynchronously
sending/retrieving files in a protocol independent manner. We're just
preparing the release right now (Sat/Sun), which will very shortly be
available at http://www.eclipse.org/ecf/downloads.html but the
plugins/projects are available via attached project set file. See the
new and noteworthy for some example usage code:
http://www.eclipse.org/ecf/NewAndNoteworthy.html
Also see the ECF test plugin project org.eclipse.ecf.test.datashare for
some Junit plugin test cases.
Hope to see you all at EclipseCon 2006. Please let us know if you have
thoughts/comments WRT ECF in general or with fileshare API in
particular. I hope we can work further in support of DSDP
communications needs.
Thanks,
Scott
Oberhuber, Martin wrote:
>Hi Scott,
>
>
>
>>In the mean time, how would you like ECF to best support DSDP? I've
>>been thinking that the next step for ECF is to produce a file
>>sharing/transfer API, under which we can put ftp, RSE
>>(eventually), and other pt-2-pt and multipoint file sharing
>>protocols.
>>
>>
>
>This sounds like an excellent plan.
>
>
>
>>Martin please let me know about proceeding WRT DSDP target
>>manager when you can, as I haven't been able to synch up
>>with DSDP recently.
>>
>>
>
>Not much has happened with DSDP in the meantime - for one, since
>all of us are waiting for the final OK from IBM to put RSE
>open source; looks like RSE would be the perfect base for
>future work.
>The other reason is that most DSDP participants have been
>either busy or on vacation.
>
>So, thinking about DSDP / ECF, for me it looks like the idea
>you had is the best path to follow for now.
>
>Cheers,
>Martin
>--
>Martin Oberhuber - WindRiver, Austria
>+43(662)457915-85
>
>
>
>
>>-----Original Message-----
>>From: Scott Lewis [mailto:slewis@xxxxxxxxxxxxx]
>>Sent: Dienstag, 6. September 2005 18:31
>>To: Oberhuber, Martin
>>Cc: David Dykstal
>>Subject: Re: FW: structuring projects and RSE function
>>
>>Hi Martin,
>>
>>David did respond this am with basically what you say...it's going to
>>take them a bit more time.
>>
>>David says:
>>
>>Ideally (and it sounds like
>>this is possible) we can wrap datastore in ECF clothes and
>>still have it
>>communicate with the datastore peers be they wrapped or not.
>>
>>David...yes, it should be possible to create an ECF 'wrapper' plugin
>>that uses RSE and have it communicate with non-Eclipse-based RSE
>>servers. We are already doing this with the XMPP/jabber ECF provider
>>(which communicates with the Jive messenger server).
>>
>>In the mean time, how would you like ECF to best support DSDP? I've
>>been thinking that the next step for ECF is to produce a file
>>sharing/transfer API, under which we can put ftp, RSE
>>(eventually), and
>>other pt-2-pt and multipoint file sharing protocols.
>>
>>BTW, we just did a new stable release 0.4.0, which has a simplified
>>container API (i.e. there is now a super interface for
>>ISharedObjectContainer called IContainer, which does not have
>>any shared
>>object semantics...but does have basic connect/disconnect
>>(renamed from
>>join/leave) semantics. There is also a ContainerFactory
>>which creates
>>instances of IContainer). We also simplified the ECF namespace
>>extension point.
>>
>>Martin please let me know about proceeding WRT DSDP target
>>manager when
>>you can, as I haven't been able to synch up with DSDP recently.
>>
>>Thanks,
>>
>>Scott
>>
>>Oberhuber, Martin wrote:
>>
>>
>>
>>>Hi Scott,
>>>
>>>has David answered yet? - The RSE is not open source yet,
>>>the process at IBM will take just a bit more time.
>>>
>>>I guess that once it is open source, David will contact
>>>you again.
>>>
>>>Cheers,
>>>Martin
>>>--
>>>Martin Oberhuber - WindRiver, Austria
>>>+43(662)457915-85
>>>
>>>
>>>
>>>
>>>
>>>
>>>>-----Original Message-----
>>>>From: Scott Lewis [mailto:slewis@xxxxxxxxxxxxx]
>>>>Sent: Mittwoch, 31. August 2005 16:57
>>>>To: David Dykstal
>>>>Cc: Oberhuber, Martin
>>>>Subject: Re: FW: structuring projects and RSE function
>>>>
>>>>Hi David/Martin,
>>>>
>>>>As quickly as practical, I would like to persue using RSE to
>>>>implement
>>>>an ECF provider. Would this be possible? Is IBM able/willing to
>>>>release RSE under the EPL (or DSDP and/or ECF)?
>>>>
>>>>In terms of mechanics...how do I get access to the RSE
>>>>codebase to begin
>>>>this technical effort?
>>>>
>>>>Thanksinadvance,
>>>>
>>>>Scott
>>>>
>>>>
>>>>David Dykstal wrote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>Scott --
>>>>>
>>>>>Here's a quick description of what we're talking about. I'm
>>>>>
>>>>>
>>>>>
>>>>>
>>>>just curious
>>>>
>>>>
>>>>
>>>>
>>>>>if it make sense to add something like this to ECF? Maybe
>>>>>
>>>>>
>>>>>
>>>>>
>>>>not now, but
>>>>
>>>>
>>>>
>>>>
>>>>>perhaps later? We've built several services on top of this
>>>>>
>>>>>
>>>>>
>>>>>
>>>>and will be
>>>>
>>>>
>>>>
>>>>
>>>>>bringing it into the TM project along with RSE if we get our final
>>>>>clearances from the DSDP PMC and IBM. However, it might
>>>>>
>>>>>
>>>>>
>>>>>
>>>>have a broader
>>>>
>>>>
>>>>
>>>>
>>>>>applicability than just TM.
>>>>>
>>>>>--------------------
>>>>>
>>>>>The DataStore communications framework is a communications
>>>>>
>>>>>
>>layer, an
>>
>>
>>>>>in-memory data repository and a pluggable tooling framework.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>It is build on
>>>>
>>>>
>>>>
>>>>
>>>>>sockets and provides a general mechanism for communicating
>>>>>
>>>>>
>>changes to
>>
>>
>>>>>structured data with minimum talk -- keeping two sides of a
>>>>>
>>>>>
>>>>>
>>>>>
>>>>connection in
>>>>
>>>>
>>>>
>>>>
>>>>>sync. You can think of DataStore as having two "channels"
>>>>>
>>>>>
>>- one for
>>
>>
>>>>>structured data and one for raw bytes.
>>>>>
>>>>>The structured data channel is used to synchronize the
>>>>>
>>>>>
>>in-memory data
>>
>>
>>>>>repositories of the client and server. When this data goes
>>>>>
>>>>>
>>>>>
>>>>>
>>>>over a socket,
>>>>
>>>>
>>>>
>>>>
>>>>>it is sent in XML form. Because commands and their responses are
>>>>>represented as structured data, this channel facilitates the
>>>>>
>>>>>
>>>>>
>>>>>
>>>>client-server
>>>>
>>>>
>>>>
>>>>
>>>>>conversation. Commands that are sent from the client to the
>>>>>
>>>>>
>>>>>
>>>>>
>>>>server are
>>>>
>>>>
>>>>
>>>>
>>>>>handled by "miners" (server -side plugins). Each available
>>>>>
>>>>>
>>>>>
>>>>>
>>>>type of command
>>>>
>>>>
>>>>
>>>>
>>>>>is contributed by a miner so the mapping between a command
>>>>>
>>>>>
>>>>>
>>>>>
>>>>instance and the
>>>>
>>>>
>>>>
>>>>
>>>>>miner that handles it is implied. Requesters on the client
>>>>>
>>>>>
>>>>>
>>>>>
>>>>may choose to
>>>>
>>>>
>>>>
>>>>
>>>>>be notified of changes made to a particular object on the
>>>>>
>>>>>
>>>>>
>>>>>
>>>>server and then,
>>>>
>>>>
>>>>
>>>>
>>>>>when a change has been detected, react according to whatever
>>>>>
>>>>>
>>>>>
>>>>>
>>>>requirements
>>>>
>>>>
>>>>
>>>>
>>>>>there may be.
>>>>>
>>>>>The raw bytes channel is used to transfer an arbitrary array
>>>>>
>>>>>
>>>>>
>>>>>
>>>>of bytes from
>>>>
>>>>
>>>>
>>>>
>>>>>client to server or vice-versa. The bytes may be either
>>>>>
>>>>>
>>>>>
>>>>>
>>>>transferred as
>>>>
>>>>
>>>>
>>>>
>>>>>straight binary or text, which is subject to codepage
>>>>>
>>>>>
>>transformation
>>
>>
>>>>>between the sides. On both the client and server ends of
>>>>>
>>>>>
>>>>>
>>>>>
>>>>this channel are
>>>>
>>>>
>>>>
>>>>
>>>>>"byte stream handlers". Different byte stream handlers can
>>>>>
>>>>>
>>>>>
>>>>>
>>>>be registered
>>>>
>>>>
>>>>
>>>>
>>>>>in the DataStore so that the bytes of a transfer can be
>>>>>
>>>>>
>>>>>
>>>>>
>>>>routed to any one
>>>>
>>>>
>>>>
>>>>
>>>>>of these depending on what needs to be done with the bytes.
>>>>>_______________________
>>>>>David Dykstal
>>>>>david_dykstal@xxxxxxxxxx
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> Scott Lewis
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> <slewis@composent
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> .com>
>>>>>
>>>>>
>>>>>
>>>>>
>>>> To
>>>>
>>>>
>>>>
>>>>
>>>>> "Oberhuber, Martin"
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> 08/04/2005 09:52
>>>>>
>>>>>
>>>>>
>>>>>
>>>><Martin.Oberhuber@xxxxxxxxxxxxx>
>>>>
>>>>
>>>>
>>>>
>>>>> AM
>>>>>
>>>>>
>>>>>
>>>>>
>>>> cc
>>>>
>>>>
>>>>
>>>>
>>>>> David
>>>>>
>>>>>
>>>>>
>>>>>
>>>>Dykstal/Rochester/IBM@IBMUS
>>>>
>>>>
>>>>
>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>> Subject
>>>>
>>>>
>>>>
>>>>
>>>>> Re: FW: structuring
>>>>>
>>>>>
>>>>>
>>>>>
>>>>projects and
>>>>
>>>>
>>>>
>>>>
>>>>> RSE function
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>Hi Martin and David,
>>>>>
>>>>>Oberhuber, Martin wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>Hi Scott / David,
>>>>>>
>>>>>>did you talk about "datastore and ECF" yet?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>No, not yet. Would like to talk sometime soon David?
>>>>>
>>>>>Thanks,
>>>>>
>>>>>Scott
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>Cheers,
>>>>>>Martin
>>>>>>--
>>>>>>Martin Oberhuber - WindRiver, Austria
>>>>>>+43(662)457915-85
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>-----Original Message-----
>>>>>>>From: Scott Lewis [mailto:slewis@xxxxxxxxxxxxx]
>>>>>>>Sent: Freitag, 22. Juli 2005 23:26
>>>>>>>To: Oberhuber, Martin
>>>>>>>Subject: Re: FW: structuring projects and RSE function
>>>>>>>
>>>>>>>Hi Martin,
>>>>>>>
>>>>>>>Just FYI...I"m on a couple of days of vacation (today Friday)
>>>>>>>and Sat so
>>>>>>>that's why I'm not in immediate touch.
>>>>>>>
>>>>>>>At first blush it seems like this 'datastore' transport probably
>>>>>>>appropriate for ECF (as a specific provider), if they are
>>>>>>>able/willing
>>>>>>>to do that. I would love to talk with them about that and
>>>>>>>see how that
>>>>>>>might be done.
>>>>>>>
>>>>>>>Thanks!
>>>>>>>
>>>>>>>Scott
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>ThanksOberhuber, Martin wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>Hi Scott,
>>>>>>>>
>>>>>>>>Dave wants to know if the existing "datastore" transport
>>>>>>>>that they are using in their Remote System Explorer should
>>>>>>>>be contributed as part of the RSE/TargetManagement project,
>>>>>>>>or as part of ECF.
>>>>>>>>
>>>>>>>>What do you think?
>>>>>>>>
>>>>>>>>Cheers,
>>>>>>>>Martin
>>>>>>>>--
>>>>>>>>Martin Oberhuber - WindRiver, Austria
>>>>>>>>+43(662)457915-85
>>>>>>>>
>>>>>>>>-----Original Message-----
>>>>>>>>From: David Dykstal [mailto:david_dykstal@xxxxxxxxxx]
>>>>>>>>Sent: Donnerstag, 21. Juli 2005 18:17
>>>>>>>>To: Oberhuber, Martin
>>>>>>>>Subject: structuring projects and RSE function
>>>>>>>>
>>>>>>>>Martin --
>>>>>>>>
>>>>>>>>Two ideas I'd like to run by you:
>>>>>>>>
>>>>>>>>(1) We have a requirement to be able to use RSE in our
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>products. If we
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>make it a part of TM, it will need to be structured in such
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>a way that
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>we
>>>>>>>>can extract the piece of the TM subproject that is just
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>the RSE. I
>>>>
>>>>
>>>>
>>>>
>>>>>>>>don't
>>>>>>>>see this as a problem since it is similar to the way folks
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>extract SWT
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>from
>>>>>>>>the platform to run standalone projects that don't use
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>RCP. However,
>>>>
>>>>
>>>>
>>>>
>>>>>>>>would
>>>>>>>>it make sense to have RSE be a separate subproject under
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>DSDP, or, if
>>>>
>>>>
>>>>
>>>>
>>>>>>>>subprojects can have subprojects -- a project under TM.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>This would
>>>>
>>>>
>>>>
>>>>
>>>>>>>>perhaps
>>>>>>>>allow for greater isolation and ease of packaging.
>>>>>>>>
>>>>>>>>(2) RSE has a communication layer called "datastore".
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>This is really
>>>>
>>>>
>>>>
>>>>
>>>>>>>>two
>>>>>>>>layers -- a generic object sharing layer and a set of
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>services built on
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>top
>>>>>>>>of that for talking about files, commands, and processes.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>I'm wondering
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>if
>>>>>>>>it makes sense to have some or all of this contributed
>>>>>>>>
>>>>>>>>
>>through ECF
>>
>>
>>>>>>>>rather
>>>>>>>>than through DSDP. What do you think?
>>>>>>>>
>>>>>>>>_______________________
>>>>>>>>David Dykstal
>>>>>>>>david_dykstal@xxxxxxxxxx
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>
>>
>>
<?xml version="1.0" encoding="UTF-8"?>
<psf version="2.0">
<!-- Required Eclipse CVS repository connections: -->
<!-- :pserver:anonymous@xxxxxxxxxxxxxxx:/home/technology -->
<provider id="org.eclipse.team.cvs.core.cvsnature">
<project reference="1.0,:pserver:dev.eclipse.org:/home/technology,org.eclipse.ecf/plugins/org.eclipse.ecf,org.eclipse.ecf"/>
<project reference="1.0,:pserver:dev.eclipse.org:/home/technology,org.eclipse.ecf/plugins/org.eclipse.ecf.discovery,org.eclipse.ecf.discovery"/>
<project reference="1.0,:pserver:dev.eclipse.org:/home/technology,org.eclipse.ecf/plugins/org.eclipse.ecf.doc,org.eclipse.ecf.doc"/>
<project reference="1.0,:pserver:dev.eclipse.org:/home/technology,org.eclipse.ecf/plugins/org.eclipse.ecf.example.clients,org.eclipse.ecf.example.clients"/>
<project reference="1.0,:pserver:dev.eclipse.org:/home/technology,org.eclipse.ecf/plugins/org.eclipse.ecf.example.collab,org.eclipse.ecf.example.collab"/>
<project reference="1.0,:pserver:dev.eclipse.org:/home/technology,org.eclipse.ecf/plugins/org.eclipse.ecf.example.hello,org.eclipse.ecf.example.hello"/>
<project reference="1.0,:pserver:dev.eclipse.org:/home/technology,org.eclipse.ecf/plugins/org.eclipse.ecf.example.provider,org.eclipse.ecf.example.provider"/>
<project reference="1.0,:pserver:dev.eclipse.org:/home/technology,org.eclipse.ecf/plugins/org.eclipse.ecf.fileshare,org.eclipse.ecf.fileshare"/>
<project reference="1.0,:pserver:dev.eclipse.org:/home/technology,org.eclipse.ecf/plugins/org.eclipse.ecf.datashare,org.eclipse.ecf.datashare"/>
<project reference="1.0,:pserver:dev.eclipse.org:/home/technology,org.eclipse.ecf/plugins/org.eclipse.ecf.provider.fileshare,org.eclipse.ecf.provider.fileshare"/>
<project reference="1.0,:pserver:dev.eclipse.org:/home/technology,org.eclipse.ecf/plugins/org.eclipse.ecf.provider.datashare,org.eclipse.ecf.provider.datashare"/>
<project reference="1.0,:pserver:dev.eclipse.org:/home/technology,org.eclipse.ecf/plugins/org.eclipse.ecf.presence,org.eclipse.ecf.presence"/>
<project reference="1.0,:pserver:dev.eclipse.org:/home/technology,org.eclipse.ecf/plugins/org.eclipse.ecf.provider,org.eclipse.ecf.provider"/>
<project reference="1.0,:pserver:dev.eclipse.org:/home/technology,org.eclipse.ecf/plugins/org.eclipse.ecf.provider.jmdns,org.eclipse.ecf.provider.jmdns"/>
<project reference="1.0,:pserver:dev.eclipse.org:/home/technology,org.eclipse.ecf/plugins/org.eclipse.ecf.provider.xmpp,org.eclipse.ecf.provider.xmpp"/>
<project reference="1.0,:pserver:dev.eclipse.org:/home/technology,org.eclipse.ecf/tests/org.eclipse.ecf.test,org.eclipse.ecf.test"/>
<project reference="1.0,:pserver:dev.eclipse.org:/home/technology,org.eclipse.ecf/tests/org.eclipse.ecf.test.provider,org.eclipse.ecf.test.provider"/>
<project reference="1.0,:pserver:dev.eclipse.org:/home/technology,org.eclipse.ecf/tests/org.eclipse.ecf.test.ui,org.eclipse.ecf.test.ui"/>
<project reference="1.0,:pserver:dev.eclipse.org:/home/technology,org.eclipse.ecf/plugins/org.eclipse.ecf.ui,org.eclipse.ecf.ui"/>
</provider>
</psf>
