The IP(s)/port(s) that WiaB listens on is completely configurable. Take a look at run-config.sh.example, the variables HTTP_SERVER_ADDRESSES and HTTP_SERVER_PUBLIC_ADDRESS control which address WiaB listens on, and which address WiaB uses when explicitly stating it's address to robots and such.
-Tad On Mon, Nov 22, 2010 at 2:06 PM, Mark Kovacevich < [email protected]> wrote: > Is there some way we can change the ports (or protocols) that WIAB > uses? Port 9898 or 9876 are going to blocked in the Government/ > Corporate environment, so WIAB is not going to work as it is currently > configured. > > I think this is related to the socket.io work that has been done, but > I couldn't find a specific mention of changing the ports for the > client/ server connection. I hope I didn't miss something obvious. > > Any assistance would be appreciated. > > Thanks, > Mark > > -- > You received this message because you are subscribed to the Google Groups > "Wave Protocol" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<wave-protocol%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/wave-protocol?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
