From: Bruce W. <br...@mi...> - 2003-11-09 22:46:04
|
> Yes, this is exactly what I have done. (-: > > I have it all working now. Every unit can operate simultaneously as both > a proxy server and proxy client. I have six full misterhouse units all > operating > in a mesh (mix of linux and windows), each sharing all the available > resources > in the other units. I had to make a few tweaks to the bin/mh code to get > all > this to work. I'd like to have these changes incorporated if > possible. If so, how do I get the changes to you? Great! Lets try simply sending me the update files. I can diff them here and either take them as is or merge in the changes. > I added a parameter to the set proxy_server socket such that > the receiver knows where the message came from. This was most > critical for debugging the mesh. I needed to make this the first > parameter > in the socket data. I tried to make it the last parameter to remain > backwards compatible but I couldn't figure out how to make > it work; maybe you'll understand the issue. If I pass another parameter > through the proxy socket after the @data array, the parameter never gets > split properly on the other side. That sounds ok. > I needed to also change speak_proxy and proxy_server. I have integrated > them into a single file to not conflict with the current client/server > scheme. > I can give you what I've done if this is something of interest. > What should I call the combined file? I'm not sure. Send me what you have and if I'll let you know if I think of a better name. Bruce |