Templates Support [Re: Request for info.]

["Rudnev, Alex (OCTO)" <Al...@dc.gov>]

> -----Original Message-----
> From: Richard Jacob [mailto:jacob@apache.org]
> Sent: Thursday, November 06, 2003 12:49 PM
> To: wsrp4j-user@ws.apache.org
> Subject: Re: Request for info.
...
> > 7. The producer processes the portlet in order to generate the markup
> > required and sends it back as a rewriteable page
> >
> yes, it generates a markup fragment which can be aggregated into a page
> by the consumer.
> The URL within the fragment can either be rewritten by the consumer (as
> you say it) or the consumer may pass templates to the producer which uses
> them for URL generation.
...
> Richard

Is template mechanism supported by WSRP4J already? I presume it is not.
{ToDo / FixMe}?

As I understand, if I deploy my portlet app behind firewall, with the only
ports open outside for the portal server itself, then in order to serve
images, scripts and other resources I will need to setup some kind of
gateway service on portal side. Besides that it's probably better
performance wise to avoid parsing of the content by consumer, are those
resource urls correctly wrapped in wsrp urls currently (I believe that
action and render urls are processed correctly)?

Regards,
Ru

Re: Templates Support [Re: Request for info.]

[Richard Jacob <ja...@apache.org>]

Rudnev, Alex (OCTO) wrote:

>Is template mechanism supported by WSRP4J already? I presume it is not.
>{ToDo / FixMe}?
>
Not yet, added to ToDO.

>As I understand, if I deploy my portlet app behind firewall, with the only
>ports open outside for the portal server itself, then in order to serve
>images, scripts and other resources I will need to setup some kind of
>gateway service on portal side.
>
Or you could have your static resources on a webserver.

> Besides that it's probably better
>performance wise to avoid parsing of the content by consumer, are those
>resource urls correctly wrapped in wsrp urls currently (I believe that
>action and render urls are processed correctly)?
>
Yes they are, wsrp defines render, action and resource URL types.
There is no clear advantage of consumer URL rewriting or Producer URL 
writing.
Of course in the rewriting case you need to parse the fragments.
On the other hand templates need more bandwith (it's argumentable 
whether this hurts in an xml protocol :-) ).
In addition templates might prevent the portlets from using static content.
Imagine a link to a gif. The consumer's client might not be able to get 
to the URL of the gif because of network setup etc.
In case of consumer URL rewriting the consumer may act as a proxy for 
these resurces.

Richard