portal application design question

[Joachim Müller <jo...@wemove.com>]

Hi List.

A portal consists usually of many (psml)pages. Often you have to
transmit data between pages (i.e. page A to page B). (We are developing
a portal witch surrounds a search engine, which may imply some user
interaction known from Google & Co.)

I would like to ask you about your oppinion about the following two ways
of data exchange between pages:

1.) One method to achieve this is to store data into the session
(portlet messaging) and redirect to the other page. Portlets on the
other page can get the data from the session and do things.

pros:

+ page A does not need to know about on which page the consuming portlet
is, the portlet that expects the data can be on a page C and still gets
the data

+ the size of data is irrelevant, because it will be transported
serverside only

+ clear separation of action processing and rendering

+ security (that not important to us)

cons:

- the redirect results in one additional request/response cycle to the
browser -> performance loss (right?)

- the request is NOT bookmarkable, because the data ist not in the URL
(might be important for i.e. search engines)




2.) The data is transportet via GET/POST directly from page A to page B

pros:

+ via GET the request can be bookmarked

+ no redirect is necessary to switch pages

cons:

- data must be handled by the doView method of the portlets

- the portlet that expects the data MUST be on page B

- no separation of action processing and rendering


we discussing our heads off and need some independend response.


Thanks for your thoughts,

joachim


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org