Re: OT: WEB Pats (portals)
Mark states " To really make these
components useful, they need to be able to communicate with each other
And that was a point that book made, too...it also pointed out that for
the various WEB parts in a given app to communicate with each other is,
at the moment, a difficult undertaking.
From: Mark Wonsil [mailto:firstname.lastname@example.org]
Sent: Tuesday, April 22, 2008 7:47 AM
Cc: Ray Shahan
Subject: RE: [HP3000-L] OT: WEB Pats (portals)
> At any rate, It'd be interesting to hear if anyone out[/color]
> has (or knows of) a WEB page that's deployed WEB parts?[/color]
Microsoft's SharePoint services and SharePoint Portal is completely made
web parts. The operative term here is "Mash Up" - let users create their
web pages with the information that interests them. Both Google and
had this capability for a while. Google calls them gadgets, Java calls
Portlets and Microsoft calls them Web Parts.
Thinking outside the web browser for a minute, the rise of Rich Internet
Applications or RIAs (think iTunes) shows another target of using these
components. A software company could web enable each module and then let
have a dashboard of just of information that they need. To really make
components useful, they need to be able to communicate with each other.
have an Open A/R web part and an Open Orders web part and you choose a
customer (via another web part) then the other components need to
I think you'll be seeing more of this and the backend of these systems
use some kind of web service processing to bind it all together. Yes, it
take time for users to figure out how to manipulate them to their
that's true for any technology.
* To join/leave the list, search archives, change list settings, *
* etc., please visit [url]http://raven.utc.edu/archives/hp3000-l.html[/url] *