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

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

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

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

or an inter-embedlet address:

/EmbedletId/JPLID


>
> Topic tags:[ARCH][JAPL][WIRING][DOCS][MGMT][STRATEGY][NEWBIE]
> _______________________________________________
>
> I'd like to include a way to ID peripherals... not something strictly
> required at this point beyond the instance for identification, but I have
> dreams (possibly pipe) of being able to link multiple processors that all
> see the same set of peripherals, regardless of what processor
> they are on...
> and use any transport to talk back and forth.
>
> Anyway, I'd like to put the skeleton into the library now, and
> wanted ideas
> on how systems could be identified.
>
> Really its based on context because not all processors have Ethernet ports
> (or I'd just use the IP). I can be done at the local level with a name
> something like "proc://spi0" or "proc://i2c1" or "proc://com2" etc...
> however that doesn't work so well when there are multiple processors...
>
> It may be (read is) possible to auto-negotiate the ID of the processor
> itself when it links with another processor, and that's the best solution
> I've come up with so far... I wanted to pass it by you folks though for
> ideas.
>
> - Brill Pappin
>   Rogue Robotics
>   www.roguerobotics.com
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
> The most comprehensive and flexible code editor you can use.
> Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
> www.slickedit.com/sourceforge
> _______________________________________________
> Embedlets-developer mailing list
> Emb...@li...
> https://lists.sourceforge.net/lists/listinfo/embedlets-developer
>