Well, it would be nice if we could have something like
myXmppServer.addDomain("anotherdomain.com"). But, if it would mess things up
I would just put out registration out of xmpp protocol. Then, I would sign
in account using [email protected]/clientid. I believe it is possible to
specify the resource to be used upon authentication.On Sat, Sep 5, 2009 at 2:25 PM, Bernd Fondermann <[email protected]>wrote: > Fernando Padilla wrote: > > username is JID. > > > > JID is n...@domain > > > > you don't want to embed the clientid on the domain? > > > > [email protected] > > > > so as long as vysper will recognize all of the sub-domains properly > > it wouldn't, as far as I can tell. > > > (anyone want to comment on having vysper server deal with many > > sub-domains? or virtual hosts?) > > you would need to have more than one ServerRuntimeContext (SRC), each > serving one domain and write a clever MINABasedSessionContext which is > able to route to the right SRC. > > Having one SRC for more than one Domain requires significant > refactorings (hint: SRC.getServerEntity()) > > Patches, as always, are welcome. > > Bernd > > > > > > > On 9/3/09 11:58 PM, Ely Celino wrote: > >> Hi everyone, > >> > >> After implementing AccountManagement, I realized I need other data other > >> than user and password in addUser(user, password) function. > >> > >> My user db consolidates all my client's record. To distinguish every > >> client > >> I added client_id column. So if query for a user, I will search by > >> username > >> plus client_id. > >> > >> Of course I could use the username parameter to the addUser function by > >> concataning other information to it but we know it will be ugly. > >> > >> Is this a limitation of the AccountManagement? > >> > >> > > > >
