Re: [Embedlets-dev] Off Topic: ID'ing peripherals

[Brill P. <bri...@ro...>]

> The container should have a unique identity that could be concatenated
with
> the embedlet/JAPL id.

Sure... though I wasn't trying to come up with an ID for embedlets and it
needs to work without an embedlet system present. however that is certainly
a workable solution.

> Since the devices are likely to be at the end of a DNS, it would probably
> make sense to structure the path as a URL:
>
> http://targetDevice.mycompany.com:port/containerID/EmbedletID/JAPLID
>
> or an inter-device (non tcp/ip) subset:
>
> /containerID/EmbedletID/JAPLID

Yes, that's pretty much what I'd like to do... what I need to decide is how
the id is generated etc, and who names the container?

1-Wire devices are easy, because they have their unique 8 byte serial
numbers already, however I need some way to identify other types of
peripherals... and the particular processor they are running on. Now if I
could specify how everyone should implement their processors, I could use an
internal serial number... but I can't, and this has to work with 3rd part
devices, so the ID has to be in software (except for the 1-Wire devices).

So, the id's can be auto generated during negotiation and start-up, or they
can be named parameters in some sort of property set... for embedlets the
named approach makes sense.

I don't want to take everyone's attention away from the task at hand... just
thought I send this out and let you all stew on it, and see what kind of
ideas get generated.

- Brill Pappin