[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ecf-dev] ECF 3.4 - PLEASE READ
- From: Scott Lewis <slewis@xxxxxxxxxxxxx>
- Date: Sun, 10 Oct 2010 07:06:59 -0700
- Delivered-to: firstname.lastname@example.org
- User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:184.108.40.206) Gecko/20100915 Thunderbird/3.1.4
On 10/10/2010 5:33 AM, Markus Alexander Kuppe wrote:
On 10/10/2010 01:55 AM, Scott Lewis wrote:
A couple of other things I wanted to ask about dnssd...is there a dnssd
feature? If so, is the dnssd feature included in the
o.e.e.remoteservice.sdk.feature (i.e. ECF Remote Services Target
Components)...which is also included in the ECF sdk feature? Is it your
intention to include it in the remoteservice.sdk.feature? Seems to me
it would make sense (in the remoteservice.sdk.feature)...as the other
discovery providers are there for both the remoteservices sdk and the
ECF sdk (which includes the remoteservices sdk).
DNS-SD comes with a feature . However the problem is, that the code
is still on git. Initially we planed to do the 3.4 release from git, so
I never cared to check the code into CVS (didn't want to loose history
Now that we've postponed the move to git (again), I'm not sure I have
the resources to move the code to CVS. Especially in front of the fact
that we will move the code back to git afterwards.
So how were you thinking we would deploy dnssd for ECF 3.4? If at all
possible, I do think it should be part of the remote service sdk and the
ECF sdk for the 3.4 release...is there some way to easily create a
composite repo or some such?
Alternatively I could move the code to CVS...sufficient to build things
for 3.4...with the expectation of moving/returning to git after ESE as
Also, would it make sense to add a new set of product configurations to
the hello examples to use dnssd rather than jmdns or zookeeper? It
might make use/adoption of dnssd a little easier.
DNS-SD requires an authoritive DNS server setup, which makes a setup
slightly more complicated than just including a new launch config.
I fully understand about the dns setup requirements, but perhaps we
could use or point to necessary DNS setup (on wiki page(s) for this
example...perhaps this is already in our wiki or someplace else), and
*then* it would allow them to use a new product configuration for the
hello world exmaple. I just think that it would be helpful to have a
common example that runs on all the various discovery providers (once
configured, of course)...to get folks up and running with dnssd as
easily as possible.