Guidelines to developing a portlet that is proxied

Added by Dustin Schultz, last edited by Susan Bramhall on Aug 05, 2009  (view change)

What exactly is a proxied portlet?

A proxied portlet is a portlet who's contents are retrieved from an external location and displayed within a portlet.

It should be used to

  1. Display 'relatively' static webpages as portlets
  2. Display small subsections of already developed applications

It should not be used to

  1. Create highly interactive and dynamic portlets
  2. Create editable portlets

It is an easy way to create content within the portal, however, it should not be the main means of creating content within the portal.

Guidelines

In general, one should develop a proxied portlet as if they were creating the application to be viewed on their server.

 Also, consider these guidelines as you develop

  1. All content that is to be proxied must be XHTML compliant. Development language is a matter of choice, as long as output is XHTML compliant.
  2. All content is to be hosted and served by an external location. The content shall not reside on the portal.
  3. All references such as images, stylesheets, etc should be referenced relative to the location of the webpage
  4. Content can take advantage of styles provided by the portal

Labels

 
(None)