Fascinating!

I've just updated my wave server to changeset 146 and have both Echoey and
Probey running.  People wishing to connect with QWaveClient or Console
Client can connect on port 9876   Also, you can kick around Probey at port
8090 which I've left open with the default userid and password (foo and
bar).

I've created some waves and some blips, and discovered various fun things:

<waveid> needs to be in the full format, e.g.
orient-lodge.com!w+blDDzGUOF_iM
Probey can only add users and blips to waves that it is already a member of.
So, of course it can add users and blips to waves that it has created.
However, if someone else creates a wave, it cannot add users or blips to
that wave, unless someone in the wave adds probey.  Once Probey has been
added as a user, it can then interact the same way as if created the wave.

Now, on to the fun parts:

Right now, it appears as if probey associates a port (e.g. 8090 with a user,
e.g. probey).  What would be very nice would be if instead of using the
username used for starting the jar, it would use the username passed in
authentication, and that the authentication would allow multiple usernames.
With this, we would be very close to a RESTful interface for adding waves,
users and blips for various users.  This could be very useful in setting up
some simple gateways.  (e.g. I've got people wanting to set up a gateway for
Second Life).

Another thing that would be nice would be if we could pass a wave name
instead of getting a system generated one.  With this, and the ability to
pass a blipname, we would have at least the basic tools for creating
backup/restore and/or persistence.

Of course, to make a gateway work nicely a getwaves and getusers might help.

Thoughts?  Comments?

Aldon

-----Original Message-----
From: [email protected]
[mailto:[email protected]]on Behalf Of Anthony Baxter
Sent: Monday, January 18, 2010 7:34 PM
To: [email protected]
Subject: Re: need help with probey agent


Yep. There's also /getblips/<waveid> and /addblip/<waveid>/<some text>

It's absolute bare bones as it's designed as an automated testing tool

On Tue, Jan 19, 2010 at 10:30, James Purser <[email protected]> wrote:
> On Tue, 2010-01-19 at 11:36 +1300, James Purser wrote:
>> Hi Anthony,
>>
>> I've got probey up and running without a problem now, when I browse to
>> the port, it asks me for a username and password, any idea what these
>> might be?
>
> Actually scratch that I've found it in etc/probey.realm. So just to
> clarify, this would be the process for creating a wave and adding a
> participant
>
> [URL]:[PORT]/new
> [URL]:[PORT]/add/[waveid]/[us...@[domain]
>
> --
> James Purser
> Collaborynth
> http://collaborynth.com.au
> Mob: +61 406 576 553
> Skype: purserj1977
> Twitter: http://twitter.com/purserj
>
>
> --
> 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.
>
>
>
>



--
Anthony Baxter, [email protected]

-- 
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.


Reply via email to