[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ecf-dev] Finding a running instance
- From: Erkki Lindpere <erkki@xxxxxx>
- Date: Sat, 30 Jun 2007 22:45:59 +0300
- Delivered-to: firstname.lastname@example.org
- User-agent: Thunderbird 18.104.22.168 (Windows/20070604)
I have part of this (finding an existing instance and sending simple
strings to it) partially implemented for Padclipse ( padclipse.sf.net ),
but it doesn't implement the ECF Discovery API -- it's just a few small
classes. There's some more info in my comment to bug #4922:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=4922#c44 . I intend to
work on this some more.
But it seems like you may need something more complex for sharing data
between two instances.
Thomas Hallgren wrote:
Continuing on a thread with the same name on the equinox-dev mailing
We are looking for a lightweight mechanism that will allow one running
instance to discover other running instances on the same machine.
Ideally, we would have liked to discover _any_ eclipse instance but
since no such mechanism is provided with Eclipse (yet), we will have
to settle for finding instances where we have presence. From the looks
of it, ECF has what we need to do just that and if any service will
make it into the platform, I think it will be yours.
Our requirements are very modest. We want to find running instances on
the same machine and figure out how they are configured and on what
workspace they are running. We will already include the ECF file
transfer in our configurations.
Question is, what would be the best approach for us? Do we use the
discovery API and the zeroconf implementation? Do we provide our own
very simple implementation? Do we need the remote services API?
Perhaps we could use a shared object?
ecf-dev mailing list