>
> >The portal with its HTML code is not flexible enough to be used in more
> >complex environments as we use it.
>
> Personally I like the full URL, I dont think it is bad practise at all. I
> also like that DynamicURI, RunData and ServerData all have rich API's that
> openly exposed and available. For unique situations such as yours,
> DynamicURI can be extended to provide the funtionality needed.
>
Following this thread, it seems to me that DynamicURI can only return
absolute URL, but can be easily extended to return relative URL.
>From where I am standing, relative URLs from DynamicURI seems to be a
general functionality, and it seems silly that everyone that is behind a
firewall or something should have to write the code himself. So I think a
patch to DynamicURI, allowing this to be configured with a static function
or TurbineResources.properties would be entirely justifiable, provided of
course that it is fully backwards compatible and efficient.
My two cents,
Magnus
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
