Gautham Kasinath wrote:
> Hey Keith,
>
> The View is something which is volatile and hence can change over a
> period of time. For instance, view can be either HTML, RSS readers or
> rich clients like dream factory stuff. Hence the way I see it, the
> View is a service consumer.
> Model forms the component, yes.
> The controller forms the service interface, service governance etc.
The Jini ServiceUI design encompasses a basic idea that someone else may know
how to provide a better interface for a particular user than the original
service distributor(s). By associating a ServiceUI (including a Role
designation) with a Jini service registration, you have the ability to provide
a
different face to a service than the "default". Perhaps the most visible or
obvious ServiceUIs are Graphical User Interfaces. But, there can be others.
This mechanism in Jini is the View in an MVC sense. It lets you see the
service
with an interface that makes the most sense to you.
Because of the user of mobile code and of marshalled objects, multiple
ServiceUIs can be attached to a single service registration. Using the typed
based lookup that the Jini Lookup Service provides, you can find all of a
particular type of ServiceUI. You can also qualify that with knowledge of a
specific instance through the serviceUI, or a specific associated service type
through the service implementation interface/class.
There are lots of levels of abstraction available and lots of binding depths
associated which allow the user of a service to be as specific or abstract as
they need to be.
Gregg Wonderly
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
