I've built the Google Wave Federation Prototype Server on a Windows 2003 Server (using the OpenFire server) and found the DOS console clients dodgey given the control codes DOS consuls cannot react to, I've been working on several Linux boxes, one of which is the size of a clenched fist and known as the SheevaPlug, see: http://www.marvell.com/products/embedded_processors/developer/kirkwood/sheevaplug.jsp seeing how these might handle hosting a wave server.
My interest is in the server area. Does the recent "beta" invitation/access of September 30th include any more glimpse into the server code area? Is it basically an invite to try client code against Google's servers only? Asked another way, does the invitation allow one to connect to one's own server. I gather from the discussions about protocols that protocols are still under wraps. I'm just wondering if I invest more of my time on the code released thus far within this group, "Wave Protocol", whether I'll be that much ahead when the standards and codes are go public. I'm also wondering if the access afforded by the invitation really provides any more insight into the server/protocol issues. I really want to run some servers within my company's firewall and put them to a stress test. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
