Submit it as a patch anyway - it sounds useful to me. The instructions should be in the root repo directory. -- Nathanael Abbotts
Email: [email protected] Wave: [email protected] Twitter: @natabbotts (http://twitter.com/natabbotts) On Wed, Feb 2, 2011 at 20:23, Gerardo Lozano <[email protected]> wrote: > The bots are finally working in our local implementations and testing > environments. > > It seems that the Wave Server Domain must have a "." something ending to > have a valid address (i.e. example.com). In our testing implementations we > had an IP address and an address that didn't have a .*something* ending, so > basically any user/robot we added had a wrong address which inhibited any > robot operations. > > We modified our code to accept an IP number as a valid address. I do not > know if you guys would consider this as something worth changing, but if > so, > I'd like to submit that code. Also I'd like to suggest documenting that in > the server.config file so that testers that use the default '*local*' > address don't have the same problem we did. > > Anybody available for revisions? > > Thanks! > > Gerardo L. > > 011/1/27 Gerardo Lozano <[email protected]> > > > I'll try that, thanks much > > > > > > 2011/1/27 Yuri Z <[email protected]> > > > >> Maybe try again with fresh Wiab source code clone? Try the simple > >> configuration - i mean just rename the server.config.example to > >> server.config and run the server. If this doesn't help - I guess you > would > >> need to debug the server and see if the events are send to the robot via > >> RobotGateway. > >> > >> 2011/1/27 Gerardo Lozano <[email protected]> > >> > >> > Yes, it works in GW and demo.wave-in-a-box.org, it doesn't work on my > >> > server > >> > with those exact steps I described before. It also doesn't work on > >> > my colleague's server under Archlinux. > >> > > >> > 2011/1/27 Yuri Z <[email protected]> > >> > > >> > > It works fine for me (on my local server - Ubuntu behind router > >> without > >> > > port forwarding). Even if sometimes slow. Can you get echoey work in > >> > Google > >> > > Wave? > >> > > > >> > > 2011/1/27 Gerardo Lozano <[email protected]> > >> > > > >> > > > Thanks for all the help, I really appreciate it. > >> > > > > >> > > > But it seems that I still haven't got the grasp of it. > >> > > > > >> > > > I did the following steps in both demo.wave-in-a-box.org and my > own > >> > two > >> > > > local servers: > >> > > > > >> > > > > >> > > > - Went to /robot/register/create > >> > > > - Added echo@<server-name> > >> > > > - put the url as: http://echoey-wave.appspot.com > >> > > > - got a success page > >> > > > > >> > > > The thing is that, it works correctly in demo.wave-in-a-box.orgbut > >> it > >> > > > doesn't work in my own server. My first thought was that I needed > to > >> > > > federate but, unless I didn't understand correctly, registering > the > >> > > robots > >> > > > should remove the need to do this. Right now I am completely > >> confused > >> > as > >> > > to > >> > > > what I should do next. > >> > > > > >> > > > I am using my own computer in my work to run the server. It's an > >> Ubuntu > >> > > > 10.10 laptop. My other server is an old desktop with Archlinux, I > >> have > >> > it > >> > > > in > >> > > > my house and it runs under a home router. I forwarded several > ports > >> > > > (including 9898) so that I could access it remotely. This is going > >> to > >> > be > >> > > > the > >> > > > hardware I'll use for serving until we get a dedicated server. > >> > > > > >> > > > > >> > > > Thanks for all the help guys, > >> > > > > >> > > > Gerardo L. > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > 2011/1/25 Lennard de Rijk <[email protected]> > >> > > > > >> > > > > Hi Gerardo, > >> > > > > > >> > > > > On Mon, Jan 24, 2011 at 23:09, Gerardo Lozano < > >> [email protected]> > >> > > > wrote: > >> > > > > > >> > > > > > We registered the bots via that URL. > >> > > > > > > >> > > > > > We found some issues: > >> > > > > > > >> > > > > > > >> > > > > > - Not adding "http://"; causes uri.getHost() to be 'null' > >> > > > consequently > >> > > > > it > >> > > > > > appends null to the robotLocation string (this is > >> > > > > > > >> org.waveprotocol.box.server.robots.RobotRegistrationServlet.java) > >> > > > > > > >> > > > > > >> > > > > > >> > > > > This has been fixed in [0]. > >> > > > > > >> > > > > Greetings, > >> > > > > Lennard > >> > > > > > >> > > > > [0] > >> > > > > > >> > > > > > >> > > > > >> > > > >> > > >> > http://code.google.com/p/wave-protocol/source/detail?r=24cf7c128b2f8f791d365391cd623a1b8147fd90 > >> > > > > > >> > > > > >> > > > > >> > > > > >> > > > -- > >> > > > Gerardo L. > >> > > > > >> > > > >> > > >> > > >> > > >> > -- > >> > Gerardo L. > >> > > >> > > > > > > > > -- > > Gerardo L. > > > > > > -- > > Gerardo L. >
