13 Dec
2016
13 Dec
'16
5:14 a.m.
Great Discussion!
(BTW: welcome kevin, awesome to have you here)
We have been talking with NicoEchaniz these last days and he convinced
me about not using mDNS for multiple reasons:
* if we push this link-local information to a more centralized place,
we may be exposing our users without them being aware of that
* mDNS has proven not to be of trust on mesh networks in the past, and
we may better seek for a better (or at least intelligent for our
context) solution
So, one possible way to deal with this would be to do service
announcement instead of service discovery, and make it easy for users
with little technical experience to publish there if they wish.
That could be addressed by adding a section on lime admin page to deal
with this.
What do you think ?
Regards,
--
Nicolás Pace
http://www.linkedin.com/in/nickar
On Fri, Dec 2, 2016 at 6:56 AM, Kevin Steen <libremesh(a)kevinsteen.net>
wrote:
I think if we want reliable service tracking, we need
to go with TCP
connections.
How about not trying to detect services - just wait for them to
register? Run a daemon providing a simple REST API which :
+ allows services to register themselves
+ sends those registrations to other known instances
+ provides a client API to list known services (e.g. as an html
widget)
That way the daemon doesn't have to run on every node and
services/registries only need a simple configuration of 1 or more
'upstream' addresses.
[ Since this is my first post here, I should probably introduce
myself:
I'm a hobbyist Python programmer and GNU/Linux geek who has been
fascinated with peer-to-peer networking since I first read about
ad-hoc
mode. I've just learned how to compile LibreMesh from source and I'm
trying to set up a community network in London, UK. I'm also trying to
find a way to earn a living working on interesting stuff like this! ]
-Kevin
_______________________________________________
lime-dev mailing list
lime-dev(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-dev