This has many similarities to the project I'm currently working on: 1) Potentially many Beagles all talking to a Web Server. 2) A need for flawless remote updates 3) The usual security issues. 4) The beagles will usually be behind a firewall, and thus must initiate any communication. 5) The users will generally be non-technical, and can't be expected to troubleshoot or diagnose.
A main difference may be that our app will be connected to the Web server as continuously as possible, but must allow for the inevitable outages and will need to synchronize data. If you expect to have many users you may want to give thought to how frequently you want each beagle to try to contact the server. Every second or two seems high. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
