Hello, All!
As detailed in the last post, BlueMesh will be trying to make the move towards greater compatibility. Specifically, we're looking towards creating a Java interface that will encapsulate all of the proprietary portions of Bluetooth. So, if you are willing to write an interface class for your platform, then BlueMesh will work on it.
That's the vision. Practically, BlueMesh will have to come with a couple of common interfaces. Luckily, I found another open-source project, BlueCove, that will allow Microsoft, OS X, and a few other platforms to do just that. Specifically, I no longer have to write code for these machines specifically; I can use this program as a bridge. More importantly, I hope that BlueCove will give me some insight as to what exactly the BlueMesh interface should expect and contain, so that any interfaces can be written easily.
This task, as large as it is, is one of my greater priorities, for two reasons.
1) It will give BlueMesh greater compatibility and intercommunication
2) It will allow for testing with the library itself to be done one any one platform, and it can be a platform of choice. The Android SDK is nice enough, but doesn't allow for easy debugging. If this interface is successfully written, then BlueMesh can be tested, and eventually operated, between any two Bluetooth-enabled devices.
Wednesday, May 30, 2012
Monday, May 21, 2012
Over the summer
Hey guys,
I just wanted to write a quick post about what will be going on with BlueMesh this summer. Sean will be working on the project with RCOS at RPI and he has a lot of really awesome things that he plans to do. I will be working up by Boston this summer, but I will still try to help out as much as possible.
Some of the changes we hope to implement are as follows:
1) Port BlueMesh to Java. Currently BlueMesh only works on Android devices, we plan to port it to Java so it will run on PCs as well. This will make development much easier and quicker. Once we have a working version in Java it should be quick and painless to port it back to Android.
2) Implement message chunking. Message chunking will allow us to determine the optimum maximum size of a message and allow us to chunk messages into this maximum size in order to allow for maximum throughput.
3) Implement routing algorithm. This will allow for point to point communication rather than flooding the network with every write.
There are other changes that are also in speculation right now in addition to these three. I'm sure Sean will be updating us with his progress often and I look forward to seeing BlueMesh progress.
-Jerry
I just wanted to write a quick post about what will be going on with BlueMesh this summer. Sean will be working on the project with RCOS at RPI and he has a lot of really awesome things that he plans to do. I will be working up by Boston this summer, but I will still try to help out as much as possible.
Some of the changes we hope to implement are as follows:
1) Port BlueMesh to Java. Currently BlueMesh only works on Android devices, we plan to port it to Java so it will run on PCs as well. This will make development much easier and quicker. Once we have a working version in Java it should be quick and painless to port it back to Android.
2) Implement message chunking. Message chunking will allow us to determine the optimum maximum size of a message and allow us to chunk messages into this maximum size in order to allow for maximum throughput.
3) Implement routing algorithm. This will allow for point to point communication rather than flooding the network with every write.
There are other changes that are also in speculation right now in addition to these three. I'm sure Sean will be updating us with his progress often and I look forward to seeing BlueMesh progress.
-Jerry
Subscribe to:
Posts (Atom)