On 2/25/06, Gregg Wonderly <[EMAIL PROTECTED]> wrote:
> Ron Schmelzer wrote:
> > Wow -- very insightful response. That's quite correct. In general,
> > that's why we only have a certain amount of looseness in coupling.
> > You're always coupled at SOME level, and in this case, we have semantic
> > tight coupling, even though we might have delivery loose coupling. So,
> > can you ever truly be "decoupled"? Probably not.
>
> public interface DoesItAllNoMatterWhatYouWant extends Remote {
> public Object doItAllAsFastAsYouCan( Object val ) throws Throwable;
> }
>
> There it is, the interface that does everything.
If that is indeed an interface, then I agree, that's what I'm talking
about (though it can't quite do "everything", which I won't get into
now).
You could, for example, use it to send a pizza order, or an order for
other things, or as I mentioned, to "upload" a file to a filesystem.
Seems very useful to me.
In fact, the industry has a long history of success with this
approach. For example, EDI and MOM work exactly this way, though they
avoid giving that operation a name as you did there. They just
present it as an identified endpoint, a document going "in" to that
endpoint, and (optionally) a document coming emerging from it as a
result.
Mark.
--
Mark Baker. Ottawa, Ontario, CANADA. http://www.markbaker.ca
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/
