Ed,
> Maybe this would be better done on a per-user basis. The PortletController can
> probably be set up to know what domain it is functioning in. For selected
> users, no off-domain links would be generated.
Ideally it might be nice to have both worlds. (no idea of the implementation time here
:) ) I think if such a feature was a part of Jetspeed, you should have the ability to
define the off-domain links by user or by default behavior of the domain the
PortletController is in. That way you can say for a Jetspeed powered site behind the
firewall, the PortletController will not render off-domain links. This behavior would
be overridden if you login to to the portal and your user profile would allow for
off-domain links.
If the Jetspeed site was located outside the firewall, then the default behavior of the
PortletController would be to enable off-domain links. If a user were to login to the
site, then you would still have the option of turning on or off off-domain links.
Kinda
silly to turn off off-domain links for a portal on the outside of a firewall, but hey,
you could do it! :)
> When you're dealing with a firewall, you have an even bigger issue. Lots of
> proxy servers have evil cache systems that rarely update. So, your intranet
> content with business logic will be fine, but the internet content will most
> likely be hopelessly out of date....
Errrg... didn't think about that... I guess the server behind the firewall that
collects the off-domain RDF, et. al. files would need to bypass the proxy. Security
policy violation I know...
Thanks!
Mark
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
