Hiya. If the need is only to communicate with devices near by (eg. same network) using something like ZeroConf/Bonjour[1] for client discovery and then just implement own app specific message transfer (could be as easy as json over http) between applications should be somewhat easy undertaking. Downside is that message transfer can happen only "in realtime" if there's no other services to cache the messages if receiver is not available.
For cellular networks, one definitely would need central server.. I've been playing with idea of using some notification services like (pushalot) to do something similar you are describing. However, if the communication between the apps needs to be bi-directional, one would need to share the api keys between the apps but if you check into that sort of systems and how they are implemented, you might get ideas on how to implement similar service on your own. Setting up jabber server or even utilizing existing jabber networks for with your own payload would be 3rd option. [1] There used to be Avahi packages for harmattan, which implements zeroconf. On Fri, May 15, 2015 at 6:27 PM, Jani Nuutinen <amonti...@gmail.com> wrote: > This would strictly be through wireless communications (3G/4G, WLAN) so I > guess were' looking into usage of different networks and thus the need of > using a server to pass the messages. > So setting up a server would be an additional thing on top of everything > else that'd need some learning first. > > I took a look what MQTT has to offer and while I'm not saying I fully > understood much about the whole subject there were also some "easier to > understand" text here and there, so that I might have a slight hunch now :) > > On Thu, May 14, 2015 at 8:46 PM, Kaj-Michael Lang <mil...@tal.org> wrote: > >> On to, 2015-05-14 at 19:57 +0300, Jani Nuutinen wrote: >> > What might the most crude requirements be when looking into simple >> > device to device (/application to application) communications? >> > >> >> Depends a bit, if the devices are on the same network then you could use >> for example simple broadcast UDP packets. >> >> But if they need to be able to communicate from different networks then >> you probably need a server that they can talk to that passes any >> messages to/from them. MQTT could be one way to do it. >> >> Depends very much on what it is exactly you need. >> >> -- >> Kaj-Michael Lang <mil...@tal.org> >> >> _______________________________________________ >> SailfishOS.org Devel mailing list >> To unsubscribe, please send a mail to >> devel-unsubscr...@lists.sailfishos.org >> > > > _______________________________________________ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to > devel-unsubscr...@lists.sailfishos.org >
_______________________________________________ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
