|
Sponsored Links
Resources
Enterprise Java
Research Library
Get Java white papers, product information, case studies and webcasts
|
General J2EE
General J2EE
General J2EE
|
Messages: 0
Messages: 0
Messages: 0
Printer friendly
Printer friendly
Printer friendly
Post reply
Post reply
Post reply
XML
XML
XML
|
 |
Could this be a better approach than SOA?
In a general reply (http://www.webofweb.net/manifesto/AppletAgainstAJAX.html) to why WoW (http://www.webofweb.net http://wow.dev.java.net) chose Applet over AJAX, I starts to think a new idea about how mass software componets are being integrated nowadays, and get some new thoughts.
Briefly, I found in a common sense APIs (Application Programming Interface) are *monolayered*, even the Service Definitions in the SOA approach. I use *monolayered* to mean that they are a list of methods/functions designed to be invoked. But the functionalities of Software Components today and logics to use them are rather complicated, and mostly *multi-dimensional* - structual objects and structual logics. So the necessary effort to compact/abstract multi-dimensional logics in to monolayered public interfaces rises quickly. In many cases, the interface abstraction work and effort needed to produce good specifications for the sets of APIs get even more costly than the problem/solution itself.
So I began doubting if the way to define Software Components' behaviors as public interfaces/services is still the best, and unavoidable necessary. I name this approache as Invocation Based Interfacing, under which you always invoke to change a target component's states or get result from the component.
I then summarized an opposing approach, I named Hosting Based Interfacing. In this approach, Task Agents are transmitted between software components, to perform their desitinated duties. What's changed is that software components never have to define public (services) interfaces for repeatedly call-return rounds, instead, they publish local environments (can just simply export part of their internal logics as public, in their straight logics), to *host* Task Agents on receipt. So various Task Agents can use environments provided by their target component to accomplish their work and send results back as new Task Agents if necessary.
The raw idea has arised in my design of the Traverser/Scener Architecture (http://www.webofweb.net/webstart?r=412) for WoW. But now I see it a little clearer.
What do you think of this?
- Compl (http://www.ableverse.org - Programming By Nature)
|
|
|
|
Hot threads
Hot threads
Hot threads
|
More hot threads
More hot threads
More hot threads
|
|
Brian Goetz continues to lift the lid and peak into the inner workings of Java in Java Urban Performance Legends. In this article he exposes the fallacy behind some of the more common performance myths found in the annals of the JVM.
(92 comments,
last posted
March 14, 2008)
Bruce Tate, author of Better, Faster Lighter Java and Bitter EJB has come out with a new book called Beyond Java. Bruce has an epiphany about the future of software development. Does it include Java?
(770 comments,
last posted
September 23, 2009)
Looks like today AJAX concept have several interpretations. We can distinguish different approaches of AJAX integration. Can they co-exist within the same application? Can we talk about layered AJAX integration?
(68 comments,
last posted
May 08, 2008)
Artima has published a short article describing the Design-Time API for JavaBeans, which was recently approved as JSR 273. This API promises to bring VB-like ease to Java development, but may face a cultural bias among Java developers who tend to think more in terms of class libraries than components.
(226 comments,
last posted
February 01, 2010)
There is plenty of speculation today regarding a potential buyout of Sun Microsystems by Scott McNealy and Silver Lake Partners. How would privatization of Sun affect Java?
(16 comments,
last posted
May 15, 2009)
More hot threads »
|
|
