General click-across improvements  Creating server-side click-across portlets

Chapter 1: Developer Features

Continuous capture versus server-side click-across

Continuous capture portlets and portlets that contain server-side click-across events provide similar results—the ability to create a portlet with embedded links that display new content when clicked. For example, a portlet may have a link that returns more detailed information about an item on the top-level portlet when you click the link. However, there are differences between these two approaches.Continuous capture allows you to create a set of related pages, based on one source Web site, which is defined within a single portlet. Individual pages are accessed through links on the top-level page. As users click links, the source Web site context is maintained, including cookies, and content is extracted to each page using the continuous capture information stored when the portlet is created. Continuous capture works for remote Web site capture.In contrast, server-side click-across is built around separate, independent portlets. Each portlet can be used in its own right. The content of each portlet is defined separately, and context, such as cookies, is maintained separately. This means that the context is not preserved as you move from portlet to portlet. Each step establishes a completely separate session with the back-end Web server. Because each portlet is separate, you need not build them from the same Web site.





Copyright © 2004. Sybase Inc. All rights reserved. Creating server-side click-across portlets

View this book as PDF