Site Sponsors:
SOA ... The Easy Way! 
Any tenured resource knows that when bandwidth is not an issues & metadata overhead is necessary to formally define services, that SOAP is best. There are also times when a more efficient encoding with an implicit endpoint CRUD strategy makes REST a better choice. But for the majority of what the planet wants to do with their front ends, be our service architecture ever supported by PHP, JSP, ASP, or legacy CGI fulfilment technologies, there has ever been a far more simple, efficient, and cost effective alternative to SOAP and REST. That way is to simply encapsulate those 20-something year-old “Web Service” GET / POST data & submission bindings so as to create an API to re-use our classic HTTP endpoints.

But don't just take my word for it. Easy HTTP is an Open Source Java Project. A framework anyone can use to prove to themselves how easy it is to re-use classic GET / POST service routines from any "service oriented programming language." EasyHTTP offers us a reasonable way to take that all-important first step in creating a "Service Oriented Architecture" for our business.

After our programs are leveraging our web-legacies, what is the classic evolution away from that BUSINESS WEB to ENTERPRISE / ESB SERVICES? -Search for the word "BEST" in this blog to see what the next steps are.

[ view entry ] ( 1872 views )   |  permalink  |  related link
BEST: Official Definition "Web Services for the Rest Of Us" 
TheServerSide is interested in BEST.

BEST is also mentioned (by request & approval) in a few videos put together for a University this week.

We were also asked to create a definition - the following is coming soon to

"BEST (Business / Enterprise State Transfer) is an approach for exchanging content with a Web site by re-using traditional HTTP Forms and Protocols. For example, a single BEST Form could be used by both web browsers as well as by a programming API. By leveraging HTTP GET and POST, people as well as computer programs can use the exact same fill-out HTML Forms for managing client / server CRUD operations. Subscribers and software developers alike would need only to know the URL (Uniform Resource Locator) for the page where the HTML Form is located to either manually or automatically send and receive data via any HTTP Server.

As described in an Open Source Project as well as a series of blog posts by Randall Nagy at, BEST is an "architectural approach" that basically embraces and extends existing technologies and protocols of the Web without the need for HTTP Server update or technology re-deployment. When using a BEST approach, for example, a service that wanted to encode Enterprise Service Bus (ESB) transactions would not have to map REST CRUD operations to ESB and / or application states, or modify the HTTP Protocol. Rather, by embracing traditional HTML Forms, HTTP GET / POST Processing, as well as HTML Forms encoding conventions, BEST offers a application-centric, rather than a protocol-centric, operational encoding strategy. By migrating CRUD and other application operations to the top of the classical ISO Reference Model (ISO-RM), BEST avoids opportunities for protocol / application request and state collisions.

Because past BUSINESS legacies are embraced, and future ENTERPRISE application problems are anticipated, BEST is simpler to use - and potentially more efficient - than the well-known REST (REpresentational State Transfer), SOAP (Simple Object Access Protocol) approaches, which requires writing or using a provided server program (to serve data) and a client program (to request data,) or outright server replacement."


Also, we have an open source project related to BEST:


Here are the original articles:

Part One

Part Two

[ view entry ] ( 2178 views )   |  permalink  |  related link
New Java Resources 
For those who are not part of this weeks class on Java, feel free to ignore this post.

For everyone else, in order to demonstrate a few Java 7 annotation concepts, Friday’s labs will require additional libraries:

Java 1.7: SDK 7.17

Spring: Version 3.2.1

Log4J: Version 1.2.5

Commons-logging: Version 1.1.1 (rename to commons-logging.jar as desired)

[ view entry ] ( 2260 views )   |  permalink  |  related link

<<First <Back | 58 | 59 | 60 | 61 | 62 | 63 | 64 | 65 | 66 | 67 | Next> Last>>