Idea
The brickd should be able to present other brickd's as if they were locally connected USB-Devices.
Why should you want this?
Because at least when you ship the WiFi-Extension there will be the demand to use it with all old code. The old code does not need to care about relations between IPConnections and devices. One solution to this would be to allow a Brickd to "collect" several other brickd's (e.g. a WiFi-Brick) and present them as local devices.
Who will do this?
Probably me. I am currently looking into the code of the brickd. This is a little pain in the neck, but however some comments made me smile ^^
Is that possible?
You might know the answer, I don't. My current goal is to find out if this is generally possible. So those are my main questions:
- Do you think this is possible?
- Do you want to see such a feature? That means: Would you pull it if it works?
I would probably not start coding here, if you say you'd never want such a feature.
Idea
The brickd should be able to present other brickd's as if they were locally connected USB-Devices.
Why should you want this?
Because at least when you ship the WiFi-Extension there will be the demand to use it with all old code. The old code does not need to care about relations between IPConnections and devices. One solution to this would be to allow a Brickd to "collect" several other brickd's (e.g. a WiFi-Brick) and present them as local devices.
Who will do this?
Probably me. I am currently looking into the code of the brickd. This is a little pain in the neck, but however some comments made me smile ^^
Is that possible?
You might know the answer, I don't. My current goal is to find out if this is generally possible. So those are my main questions:
I would probably not start coding here, if you say you'd never want such a feature.