zagor
|
Posted: October 20, 2008 11:18 by zagor
|
|
Hi, i am quite happy to see this project i did different attempts to build with the same goal of this project. I would like to share my experience on it, i hope it can be helpful. I suppose you want to use a server centric approach, i mean the different devices take information on others from the server and by the server they communicate one to the other, and not a peer to peer approach. first attempt Jini network. Pros: 1. it has interesting projects related to graphical rappresentation of the network. so possibile to visualize nodes of the network and building the rules to relate the nodes. 2. it was born to buid network of devices. Cons. 1. RMI communication.. network crazyness 2. It's a myth that it runs on devices. since it is based on JavaSE, not JavaME, so if you don't have so hardware supported devices, it will never work on your mobile. 3. it's based on direct communication from device to device, only the discovery it's made form a central server. Jabber. I am experimenting a solution with a jabber server and pus/sub module. Pros. 1. standard text protocol, network friendly. 2. it runs everywhere and has an implementation on every programming language and device, i thikn even on mars robots  3. it has the concept of presence. 4. it's easy to plug a rules engine, to dispatch messages. Cons. 1. it is slow. 2. there is no way to create a direct connection to devices. I hope these ideas can be helpful and it's interesting to know your opinion. Luca |
architecture notes
2 posts
Replies: 1 - Last Post: October 20, 2008 15:45
by: Hildeberto Mendonca
by: Hildeberto Mendonca
showing 1 - 2 of 2
Hildeberto Mendonca
|
Posted: October 20, 2008 15:45 by Hildeberto Mendonca
|
|
Hi Luca, I'm also very happy with your comments. Thank you! We will strongly take it into consideration. Please, consider to watch this project and subscribe in some of our mailing lists. About the project, well, we started considering a server centric approach. We still follow this direction, which is part of the first version to be released soon, but we are also thinking about a low level communication, which we found in another project called OpenInterface (http://openinterface.org). About the network approach, we didn't considered Jini or Jabber. First because different devices don't need to take information from each other. Actually, all devices will submit collected data to a TCP/IP port and many agents will analyze all received data from all connected devices. If the device is not able to transmit data, a component should be developed to transmit date through the network. Second, we are not inclined to adopt a particular framework in the foundation of the architecture to avoid unexpected overheads. We aim to implement a particular solution for the project's needs. It may be an interesting challenge, but the response time is very important for us. Each connection to the server starts a thread called channel. Each channel is considered as a new modality. All channels are processed in parallel by agents that will try to "understand" what is been received. Your comments opened my mind for other possibilities. I will recheck if my decision to discard peer-to-peer communication was correct. At least for some cases it could be a good approach. Thank you again! Regards, Hildeberto Mendonça |
Replies: 1 - Last Post: October 20, 2008 15:45
by: Hildeberto Mendonca
by: Hildeberto Mendonca
