[misterhouse-users] Re: Distributed Proxies

[Jim D. <jim...@rc...>]

Bruce,

> I can see where this would be tricky.   If this is still an issue you
> haven't resolved, one solution would be to set a global flag when in the
> check_for_proxy_data function and have the
code/common/proxy/proxy_server.pl
> hook functions return if that flag is set.  Make sense?

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?

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.

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 like the full client/server approach.  This allows me to directly share
all of my code pieces for the "collective" and not have to worry about
sending voice commands around from the main mh unit.  There is no
"main mh" unit anymore.

Jim

"Bruce Winter" <br...@mi...> wrote in message
news:NAB...@mi......
> > All my units can speak and play to of the other units (rooms).  Each
room
> > can access the services provided by the main mh unit, cm11, cm17,
> > w800, etc.
> > And the main mh unit can access the services provided in the other
units.
> > Each operates as an independent peer.  I hope to build intercom
> > functionality soon; is this already available in mh?
>
> Nope, I don't think anyone has tried an intercom.   We have the room=
speak
> parm for directing speech, but have not tried capturing and forwarding
> speech.
>
>
> > I have a sticking point which I need help with.  The issue concerns a
loop
> > which
> > occurs when a proxy client receives information from a proxy server
serial
> > port.
> > ....
> > This loop is activated when a proxy server sends serial data to a proxy
> > client.
> > What happens is the client ends up calling Serial_data_hooks which
results
> > in the data being sent back to the proxy server.  This in turn
> > causes a loop
> > because the proxy server then sends the data again; proxy_server.pl
calls
> > send_serial_data, which calls proxy_send and we start all over.
> >...
> > I get such a headache dealing with these loops, its like a bad space
> > time continuum nightmare (-:
> >
> > Jim
>
> I can see where this would be tricky.   If this is still an issue you
> haven't resolved, one solution would be to set a global flag when in the
> check_for_proxy_data function and have the
code/common/proxy/proxy_server.pl
> hook functions return if that flag is set.  Make sense?
>
> Let me know if you want to add that or want me to add it.
>
> Bruce
>
>
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: ApacheCon 2003,
> 16-19 November in Las Vegas. Learn firsthand the latest
> developments in Apache, PHP, Perl, XML, Java, MySQL,
> WebDAV, and more! http://www.apachecon.com/
> ________________________________________________________
> To unsubscribe from this list, go to:
http://sourceforge.net/mail/?group_id=1365
>
>