[3466] in Software Accessibility Project email archive
The extra data itself can come from different sources: it can be entered by the user or it can be replicated from another application via Data Replication.
daemon@ATHENA.MIT.EDU (Arabella Austin)
Tue Jun 12 00:27:16 2007
Message-ID: <466E2088.7020808@jeffco.us>
Date: Tue, 12 Jun 2007 09:56:48 +0530
From: Arabella Austin <apkt@jeffco.us>
MIME-Version: 1.0
To: sw-access@mit.edu
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
COULD THIS BE THE NEXT HOMERUN? WATCH VPSN LIKE A HAWK STARTING TUESDAY
JUNE 12th!
Company: Vision Airships, Inc.
Symbol: VPSN
Price: 0.50
5-day Target: 1.50
Current Rating: Strong Buy
Vision Airships is set to become a worldwide operator of blimps used for
advertising around the world. News Is Out! Vision Airships Inc.
Expansion Plans in the Works. ADD VPSN TO YOUR RADAR NOW, AND WATCH IT
TRADE ON TUESDAY 12th!
Hey, Microsoft listens very actively to developers, the ideas are just
owned by MS in the end. In case of BTW, it was this one related to the
vendor race in the SOA space: We don't know where we are going but we
want to get there first! But this also means that the system has fewer
means of detecting our mistakes.
Distributed components promised to hide remote communication from the
developer by making the remoteness "transparent".
It is nice to see that we are now getting tool support to let people
work with aspects effectively.
David Orchard has given us a nice definition of the ultimate loosely
coupled solution by stating: "How do you make two systems loosely
coupled? Well, at least the ones we had with the distributed component
architectures.
Also, it might keep internal state data to be carried over to the
processing of the reply message.
Strangely they quote me as saying "forget about SOAP and design
patterns". Integration Testing As a result, integration testing is more
critical than ever with loosely coupled, composable systems. She was
really asking for it to the extend that one wondered whether it was a
setup.
It is nice to see that we are now getting tool support to let people
work with aspects effectively.
Here is a brief list of items I came up with. More coupling gives us
efficiency and simplicity but can also introduce rigidity and
brittleness. Frank Leymann, one of the co-creators of BPEL, invited me
to speak on SOA from a developer perspective. For example, one can build
fine SOAs using CORBA, even though the nagging question might be "why
would you? She was really asking for it to the extend that one wondered
whether it was a setup. The need for new logic makes approaches such as
All Purpose Fields or Extension Tables tougher because now you need to
be able to add code to the application that deals with the new, generic
fields.
I hope that this brief overview illustrates the fact that there is often
more to statefulness and statelessness than initially meets the eye.
Here is a brief list of items I came up with. XQuery A nice talk by
Jason Hunter.
It will also be interesting to see what the next best thing will be.
Hao He has defined the following architectural constraints for SOAs: A
small set of simple and ubiquitous interfaces to all participating
software agents.
Also, it might keep internal state data to be carried over to the
processing of the reply message.
I think it is time for me to start blogging a bit more about BPEL, so
stay tuned.
Social Events What would a conference in Vegas be without all the dirty
stories?
DC architectures typically link components directly to one another,
making the solutions brittle. Anyway, the BTW conference is held every
other year.
What if I don't have all required information available to assemble a
single document? How so, you might ask.
The elements of an SOA are services, self-contained modules that are
universally accessible and advertise their interface contracts via some
form of registry.
Naturally, it is difficult to test explicitly for unforeseen scenarios.
What if I need a reply back? So it seems that SOAs solve all our
problems. I have seen an interesting variation of this pattern quite
frequently in real life.
It will be interesting to see where the Web service evolution balances
out or whether we'll hit another curb.
In fact, there is enough to be said about this topic that I'll leave
most of it for a separate posting. It is also equally hotly debated. The
blackboard will return a reference to any entry that matches the
request. A conversation coordinator may be required to make decisions
that require knowledge of the whole conversation. How closely do you
want to tie outgoing events to a specific messaging infrastructure? This
model turned out to be quite complex given the inherent complexity that
distributed architectures add into the mix.
I think it is time for me to start blogging a bit more about BPEL, so
stay tuned. I think the last truly "stateless" computer I can think of
are analog computers, wired together from transistors and resistors.
Recoverable State One reason state might be irrelevant is because it is
below the agreed upon level of abstraction.
But we can be assured that once SOAs reach wide adoption all marketing
departments are itching to define the next major trend. Service-oriented
Architectures If you have a Web browser and are interested in Web
services you probably have not escaped the discussion around SOA, REST,
Web services etc. Developing an enterprise application is as much about
extensibility and integratability as it is about core application
functionality.
The elements of an SOA are services, self-contained modules that are
universally accessible and advertise their interface contracts via some
form of registry. One object can control the lifetime of remote objects,
pass references, and rely on polymorphism and inheritance.
