Martin Cooper wrote: > I do have the book - I just haven't had time to read much of it yet. ;-) I > didn't think I was interested in portals, but it looks like I might be > interested in portal technology put to a different use...
Came across this on the way to something lese. Thought it might interest you: What essential services does a portlet API need to provide? * Discovery * Authorization * Profiles (user customization, skins) * Presentation fragments (scrape) * Resource configuration, application and user (profiles?) I've had team managers tell me that what they would really like to do is have each group working on a portlet, and then assembly them into an application. Which I believe is what you are after. A related idea is leveraging single-logon for multiple applications. So, you might offer a service via a traditional RSS portlet, but when they click through they actually land in a whole 'nother application that's sharing the login protocal and database. -- Ted Husted, Husted dot Com, Fairport NY USA. -- Building Java web applications with Struts. -- Tel +1 585 737-3463. -- Web http://www.husted.com/struts/ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
