on 2014/07/08 10:20, Aline Manera wrote:
On 07/07/2014 08:51 PM, Sheldon wrote:
On 07/08/2014 03:44 AM, Aline Manera wrote:
On 07/04/2014 02:24 PM, Aline Manera wrote:
On 07/03/2014 12:03 PM, Sheldon wrote:
On 06/05/2014 08:53 PM, Aline Manera wrote:
On 04/17/2014 10:38 AM, Sheldon wrote: > I'd like to talk about how to discover Kimchi peers. > > Now I just talk about discover a peer in a same network here. > > I will use a local multicast subnetwork address > <http://en.wikipedia.org/wiki/Multicast_address#Local_subnetwork> to > find peers in one network. > Choose 224.0.0.132 as the kimchi multicast address, and 8000 as the > port. >
How will you choose the multicast address?
You can not assume all Kimchi servers is running in the default port 8000 The user can change it.
In my mind I think we should send a broadcast message in the network and wait for the responses. And we need to add a hook in Kimchi to respond to those messages with the IP and port number Kimchi is running.
zhengsheng suggested *upnp-inspector. * looking into *upnp-inspector
What about openSLP? Seems it is simple to use. We just need to register kimchi server on startup and unregister on shutdown
http://www.openslp.org/doc/html/IntroductionToSLP/index.html http://www.openslp.org/doc/html/UsersGuide/SlpReg.html
I've just tested openSLP and it works pretty well and attends Kimchi needs. I will send a RFC patch soon.
Thanks. Simon Jin is working on this feature.
The openSLP patches are almost done! Simon Jin can work in other task as we have a lot to do for Kimchi 1.3 :-)
Took a look at SLP. It looks exactly what Kimchi needs. I makes use of multicasting under the hood, and provide a meaningful URL scheme for the applications. -- Zhou Zheng Sheng / 周征晟 E-mail: zhshzhou@linux.vnet.ibm.com Telephone: 86-10-82454397