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.

-----Original Message-----
From: Mark Wonsil [mailto:wonsil@4m-ent.com]
Sent: Tuesday, April 22, 2008 7:47 AM
To: HP3000-L@RAVEN.UTC.EDU
Cc: Ray Shahan
Subject: RE: [HP3000-L] OT: WEB Pats (portals)

> At any rate, It'd be interesting to hear if anyone out

there
> has (or knows of) a WEB page that's deployed WEB parts?


Microsoft's SharePoint services and SharePoint Portal is completely made
up of
web parts. The operative term here is "Mash Up" - let users create their
own
web pages with the information that interests them. Both Google and
Yahoo have
had this capability for a while. Google calls them gadgets, Java calls
them
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
web
components. A software company could web enable each module and then let
users
have a dashboard of just of information that they need. To really make
these
components useful, they need to be able to communicate with each other.
If you
have an Open A/R web part and an Open Orders web part and you choose a
new
customer (via another web part) then the other components need to
refresh.

I think you'll be seeing more of this and the backend of these systems
will
use some kind of web service processing to bind it all together. Yes, it
will
take time for users to figure out how to manipulate them to their
benefit but
that's true for any technology.

Mark W.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *