FrameWork JAVA
Home
SOD – Servlet Oriented Development (SOA was taken).
Setting the stage…
SOAP, POX, REST, blah, blah, blah – Socket programming wrapped up in layers of acronyms and confusion all in the name of the ‘Next Big Thing’. In the end what is it? Nothing more than a bunch bytes, wrapped up some open format (that you better not deviate from), and being sent to a socket listener with a really important sounding name ‘Joe Blows Enterprise Application Server’.
It you want to create your own Web Server, or if you just want to see how simple they are to create, check this code out: Sun Sample Web Server
In the end, a Web Server is simply a listener that serves up Web Pages (HTML) and static content (Images, Sound files etc.).
So what about Application Servers – those must be big an scary, after look at the definition put forth my Microsoft;
“We define the category of application server as the “system software that underlies the server-based execution of shared business applications.” Just as a file server delivers files to many users, an application server makes applications—often custom-built applications—available to multiple concurrent users.”
YIKES! Really? Ok, forget that – let’s move on.
SOD – Why bother? Do we really need another Service Oriented Acronym? No, but I was bored so I decided to take a couple of days and put together a common architecture for serving up web and service content.
This site wil be dedicated to J2EE development issues.
