RE: [Embedlets-dev] Re: Is/Are Embedlets alive?

[Christopher S. <cs...@oo...>]

I just spent some time evaluating the jddac code release. Here are my
conclusions:

1. Jddac addresses many of the issues the embedlets project addresses
including:
	Component/Containment
	Configuration
	Lifecycle
	Communication
	Threading

2. JDDAC adds several important aspects
	Data Model
		- ArgArray
	Network communication (publish/subscribe over http)
	Java Tranducer Interface (JTI)
	Server Platform - J2EE based colection and presentation service
3. Embedlets has the following advantages:
	System logging
	Working implementation for Ajile and Dallas processors
	Hierarchical Persistence model (embedlets/persistence)

Missing in the current JDDAC release is client/server model that is
appropriate for inter-component communication in an embedded application.
(Embedlets has a pub/sub model as well although we had discussed a
client/server model).

The big advantage of JDDAC is the backing by Sun and Agilent and the
conformity to the IEEE 1588 standard. My recommendation would be to make the
Embedlets project a part of the JDDAC 'incubator' and rework Outpost as a
J2ME appropriate implementation.


Some notes on the current JDDAC release:


The xml configuration files are 'flat' and are difficult to navigate with a
tree-based editor because everything is an 'arg'.  This is not a major
drawback but I prefer a more structured object diagram such as I submitted
in the embedlets/persistence model.

The sample application does not run without some debugging of the ant builds
and the getting started documentation produces none-compilable code. After
debugging I did manage to get things running.

Chris



-----Original Message-----
From: emb...@li...
[mailto:emb...@li...]On Behalf Of Ted
Kosan
Sent: Thursday, August 05, 2004 11:20 PM
To: emb...@li...
Subject: [Embedlets-dev] Re: Is/Are Embedlets alive?


Topic tags:[ARCH][JAPL][WIRING][DOCS][MGMT][STRATEGY][NEWBIE]
_______________________________________________

Bruce wrote:

> I'm slow on the uptake, apparently. I only recently wondered why I hadn't
> heard anything interesting from the Embedlet group, went to SourceForge
and
> there have been no new postings since April.

I wouldn't say dead but the project definitely went dormant after we hit a
brick wall trying to decide how to solve the plug-and-play peripheral
problem.
Also, we have not heard from the main architect in a while (Andrzej, are you
still out there? :-)


At that time a lot of posts were submitted which were dedicated to the idea
of
plug and play sensors and actuators and this was tied in with Brill's Cork
library.  The place where we hit a wall with this was on trying to decide
what
the protocols and standards should be for tagging the sensors and
communicating
with them.

After letting this sit for a while what eventually happened (which I do not
think most of the people on the list are aware of yet) is that Sun started
their JDDAC community (http://jddac.dev.java.net) about 5 months ago based
around the new IEEE 1451 Plug-and-play transducer standard and this standard
pretty much solves all of the problems we were discussing.



> We're revising the TILT400 schematics and putting the Embedlet project URL
> on them, at the Embedlet connector, but this may be moot if the group has
> gone dormant.
>
> TStik and TILT400 are starting to catch on - there has been a nice
increase
> in orders in the last 90 days or so. TILT400 has the Embedlet connector -
> added in specifically to support the efforts of this group.

At this point I do not think it is safe to put the Embedlet name at the
connector and as to whether or not you leave the connector itself on the
board
is a judgment call.

Ultimately I was the person who pushed for a buffered I2C connector because
I
think that it provides an enormous amount of flexibility.  In my mind it
could
provide the plug and play capability that 1-Wire does at significantly
increased speeds (especially when used with muvium devices).

What comes to mind now is that the connector would be useful for plugging
1451
devices into because that was the kind of capability we were shooting for
originally.



> So I'm just wondering what the status of the group and project is.

This is a good question.  The Embedlets code base works and now that the
JDDAC
project has some Java code that implements various parts of the new 1451
standard, perhaps it is a good time to move development forward again?


Ted



__________________________________
Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out!
http://promotions.yahoo.com/new_mail


-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Embedlets-developer mailing list
Emb...@li...
https://lists.sourceforge.net/lists/listinfo/embedlets-developer