<body><script type="text/javascript"> function setAttributeOnload(object, attribute, val) { if(window.addEventListener) { window.addEventListener('load', function(){ object[attribute] = val; }, false); } else { window.attachEvent('onload', function(){ object[attribute] = val; }); } } </script> <div id="navbar-iframe-container"></div> <script type="text/javascript" src="https://apis.google.com/js/plusone.js"></script> <script type="text/javascript"> gapi.load("gapi.iframes:gapi.iframes.style.bubble", function() { if (gapi.iframes && gapi.iframes.getContext) { gapi.iframes.getContext().openChild({ url: 'https://www.blogger.com/navbar.g?targetBlogID\x3d8907963\x26blogName\x3dWS-Comments\x26publishMode\x3dPUBLISH_MODE_BLOGSPOT\x26navbarType\x3dBLUE\x26layoutType\x3dCLASSIC\x26searchRoot\x3dhttp://ws-comments.blogspot.com/search\x26blogLocale\x3den_US\x26v\x3d2\x26homepageUrl\x3dhttp://ws-comments.blogspot.com/\x26vt\x3d-792153501087690591', where: document.getElementById("navbar-iframe-container"), id: "navbar-iframe" }); } }); </script>

WS-Comments

perspectives on open-source and web services

Tuesday, November 23, 2004

great reads

I was sent on some great reads yesterday and today by a nifty link in my great google alerts. apparently someone is already out there championing some advantages of PHP over J2EE, and it's great that a large part of their argument rests on the fact that "everything talks SOAP/HTTP... So where is the application server of the future? It is a big text pump that is embedded in the various endpoints of an enterprise. There is nothing in the middle."

'big text pump' would be a great way to summarize how languages like Perl and, to a lesser extent, PHP started. this was really enlightening to me to think of web services in this way. after all, even with all the DOM vs. SAX and in-memory vs. file-parsing, etc....XML is text. and when you're talking about advanced Web Services...it's a LOT of text. so being able to handle text files easily and efficiently is a huge advantage of PHP over heavier app platforms like J2EE and .NET even. in theory, a stripped-down lamp5 box will blow away a J2EE app server on text handling, ie. Web Services. the ease of using the text is evident by the simplicity of the extensions that handle XML.

in addition to the cool angle on PHP vs. J2EE, I was made aware of ActiveGrid, which I'm not yet sure whether to view them as a partner or a competitor of lamp5. I think ActiveGrid's purpose is to be able to create application servers that scale over a large number of small machines, as opposed to a small number of heavy machines. so I can see a partnership where ActiveGrid helps in developing lamp5 architecture such that it is suitable to spread over large numbers of small machines.

I'm going to be frequenting both of those blogs, so future postings of mine may come from links to theirs.

0 Comments:

Post a Comment

<< Home