As I understand it, we will be doing both proxy and load balancing using an ISA proxy server (which I know nothing about).
I may have solved part of the equation by setting the $link tool to RelativeTemplateLink. However, I still have an issue with $content. The default implementation (o.a.t.util.ContentURI) extends DynamicURI. There is also a RelativeDynamicURIclass. Perhaps I can figure out a way to have ContentURI extend that instead. It seems logical that should also be a RelativeContentURI class. -Mitch -----Original Message----- From: Chris K Chew [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 11, 2002 10:35 AM To: Turbine Users List Subject: RE: Relative Links > Mitch Christensen: > At the 11th hour I have been notified that our project needs to use *only* relative URLs (for load > balancing/proxy reasons). Our development team has faithfully used $link.setPage() and $content.getURI() > throughout the application, and I'm hoping that Turbine makes the use of relative URLs easy, or at a minimum, > doesn't make it impossible. > > Does anyone out there have any experience/ideas on how to do this? The problem with "relative" urls in Turbine is that there really is no single point of reference because templates and parameters look like directories to the browser. What kind of load balancing / proxying are you going to be doing? Chris -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
