|
From: Alessio B. <al...@al...> - 2001-07-26 13:40:35
|
"Martin, James S." wrote: > It seems as though it's almost an > oversite in the code that the absoulte and relative dirs are hardcoded into > the database. Well, two things: first, if the two servers are behind a load balancer hardware, it seems to me that this configuration should be kept hidden to the end user. As an example, if you have slash1.yourdomain.com and slash2.yourdomain.com as Slash balanced-servers, I, as a user, expect to access them as slash.yourdomain.com and leave the dirty work to the hardware/software. I don't want to see slash1 or slash2 in my URL since it annoys me, doesn't work well with caches, etc. So having slash.yourdomain.com in the db config seems ok to me, since it will be encoded in URLs sent back to the user, that therefore will show up again in front of the load balancer. If not, user will continue to work always on the same server, so you are just "balancing" the number of users that first access to the homepage, because from that point on URLs will have the name of a single server inside. What if a URL gets linked in some other site? What URL you print in your RSS feed file? On the other hand, relativedir can be relative, so I believe can just be '/' without the hostname. absolutedir is included in mail messages and RSS files, so it really is the main URL of your site. Unfortunately, 1.0.X was buggy in this respect and I don't know if all of them have been cleaned for 2.X. > I tried to modify the Utility.pm-- You really have to know where you put your hands... -- Alessio F. Bragadini al...@al... APL Financial Services http://village.albourne.com Nicosia, Cyprus phone: +357-2-755750 "It is more complicated than you think" -- The Eighth Networking Truth from RFC 1925 |