> 3. Hack JID rewriting stuff into the JSM, so that any to/from attributes
> get rewritten to what I want them to be.
It already does this, in the <pthcsock> element in the c2s config just
add:
<alias to="server.name"/>
It's ugly, but it does all the magic to/from replacing so that things work
just like you want :) The above is the "default" one, you can also have
multiple <alias to="real.server">what.client.uses</alias> in there.
> 4. Get clients to use SRV records for the client connection.
This should definately be a goal, but it's still very hard to do SRV
lookups in most environments. Hopefully that will change, or some simple
portable SRV lookup libraries will happen.
Although it's probably not "right" in some way, I'm a fan of using a
fallback method (if you can't do SRV) of just a normal A lookup on the
same SRV formatted record: _jabber._tcp.jabber.org. SRV gives you port
assignment and weighted and load balanced farms, which is all very nice,
but if you just can't hack it then at least having an alternative IP is
still very useful.
>
> 5. Get clients to treat the JID and the server as different entities.
Yes, it should probably have been clearer at some point that it would be
useful in clients to have an advanced option for a "proxy" or "server"
entry box, that is used only for resolving the server, much like email
clients and pop/imap.
Jer
_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev
