OK, so you are only running one server, but connecting two clients. If you are running the client in the standard windows CMD window, then the client will not render properly. From what I remember, it was basically unusable.
Try this: 1. Restart the server 2. Connect a client 3. Type "/new" 4. "/open 0" If you don't get any error at step four, then it's working. On Sat, Nov 7, 2009 at 4:23 PM, ARGold <[email protected]> wrote: > > Not exactly Tad: > > Since the run-server is configured with > > --client_frontend_hostname=(LOCAL SERVER NAME) > --client_frontend_port=9876 ^ > > That means in order to connect ANY client, whether locally or > remotely, the client must be configured with > > set WAVE_SERVER_HOSTNAME=(LOCAL SERVER NAME) > set WAVE_SERVER_PORT=9876 > > That means that the local client appears to be a remote client also. > so when I typr /new in EITHER client, no wave is created and so there > is no wave for either to /open. > > I am following the bug about needing to add a blip before adding > participants, but if configured to allow a remote client, I am not > able to create a wave at all. > > I think this may be related to the bug you are reporting. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
