Quoting "Horatio B. Bogbindero" <[EMAIL PROTECTED]>:
>
> what about URL rewriting instead? for example: mail.example.com will
> rewrite the address to either mail1.example.com or mail2.example.com?
you still need a consistent database of user-base settings across all IMP nodes.
either you use a single database shared by all your IMP servers, or you have a
way of replicating changes across all different databases of the individual IMP
servers so user info is still there if you get redirected to a different IMP
server the next time you log in.
another option is to hack IMP's code to have single logon page for all your
users, divide your user base into different but dedicated IMP machine for a user
group, and have the logon page redirect your user after login to the proper IMP
machine where his info belongs.
my gut feel is that IMP code is more manageable than squid code...correct me na
lang if i'm wrong.
actually, the reason why ateneo's imp server is quite slow is due to the slow
imap of the mail server. it's quite an anarchy, using old-style unix mbox, no
quotas, uw-imap and IMP. tagal ng load. at 500+ messages before...it was sooo
slow, compared to the student mail server which uses cyrus-style maildir...my
inbox there, with 2500+ messages was actually faster with IMP.
yun lang.
vince.
--------
This mail sent through IMP: mail.ateneo.net
_
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
To subscribe to the Linux Newbies' List: send "subscribe" in the body to
[EMAIL PROTECTED]
