[Moonbeam-users] Re: moonbeam 0.3.1

[Heiko B. <he...@op...>]

> 1. In the "Clients in the same group" query, the
> response containing the client list is in the following
> format:
> <attribute name=3D"groupmembers" value=3D"[peter, charly, karl]" />
> (Hope this line didn't confuse your mail client.)
> The format is similar when you want to get the group names.
> This means client names and group names aren't allowed to
> contain commas and/or spaces, and there may be problems
> with names containing square brackets ([]) as well. (The client
> program processes the above line using these symbols as
> separators.) Wouldn't it be nicer if the client and group names
> would be separate xml values somehow, and not a list that
> needs string processing?

i thought about that as well.=20
it is a problem with datatype conversion in general.
you can break it down into simple and comlex datatypes
for get/set iq's:

a simple type example

<attribute name=3D"myAtt" value=3D"myValue"/>

a complex type:

<user id=3D"12342">
	<name=3D"peter"/>
	<email=3D"pe...@mo...">
</user>

both types can be used as return values,
eiter as a single value or as an array of values.

i think we should support the complex types.
but this means that moonbeam needs to know a lot
more elements, or on the other hand, be able to process
unkown elments:

<iq type=3D"result">

	// put any element here

</iq>

i guess, supporting unknown elements would be the=20
best solution, since everything else means additional=20
binding classes for every element.


> 2. How does the server respond when two different clients
> want to set the same client name? Is it possible to have different
> clients/groups with the same name?

no, a client name has to be distinct throughout groups.
otherwise we run into trouble when the same names occur
in the same group and you try to send to this name.

moonbeam should tell you that the name is already taken.

> 3. "A client is always in a group and in one group only."
> But one user may run multiple clients from the same
> machine, right? Will this user be able to use the same
> client name in every client? (See previous question.)

yup, multiple client from the same host/machine,
but different names.

the names act as aliases only. for every name the server
keeps a distinct client id.=20

> 4. Is there a working Moonbeam server somewhere on the net
> where I'll be able to test my Flash client? (This is not urgent, at first
> I'll test it on my local network, but afterwards, it would be great.)

yup, i will put one on openj.net.
i always wanted it for performance testing.

> 5. A personal question: what OS do you use for testing?
> I'll need to make MB running on Debian Linux.

;)

lovely!

i am developing, working and living on debian.


> Bye,
> Marcell
>=20
> Heiko Braun wrote:
>=20
> > hi marcell,
> >
> > i started working on the default engine, called 'MUD',
> > which is going to implement the features we talked about.
> >
> > there is a preview available under
> > http://sourceforge.net/project/showfiles.php?group_id=3D48248.
> > currently only a few features are realized, but should
> > be enough to keep you busy for some days ;)
> >
> > take a look at $MB_HOME/guid/mud_cmd.pdf file.
> > you will find an overview of what the engine is capable of
> > at the moment, sample messages and an idea how the new
> > message format is going to be used.
> >
> > i also seperated the source and the lib files, to make the upgrades
> > easier. it's now sepereated into a moonbeam-src and a moonbeam.lib
> > archive.
> >
> > have fun and email me if you have any questions.
> >
> > so long,
> > heiko
> >
> > --
> > Heiko Braun <he...@op...>
> >
> >   ---------------------------------------------------------------------=
---
> >                        Name: signature.asc
> >    signature.asc       Type: Notepad File (application/pgp-signature)
> >                 Description: This is a digitally signed message part
>=20