In his entry XMLRPC vs REST vs SOAP vs CIM vs RMI vs Message Bus vs … Lots of RPC Options, Michael DeHaan opens his experience with RPC protocols and pours it out on the page.
This is based on not only a few apps like Cobbler and Func, but also past work where I’ve touched almost all of these first hand — I always seem to get stuck working on the backend server components wherever I go. This is by design — I like it there.
Michael then goes down a list of RPC protocols, noting positives (+) and negatives (-) about each based on his time working with remote procedure calling. He is the founder and lead developer for Cobbler, a next generation Linux provisioning server, and Func, a “secure (and) scriptable remote control framework and API.”
JBoss developer Adam Warski writes about Instant Facelets: changes in .xhtml and no redeploying:
If you are developing anything with Facelets/Seam/… frameworks, you probably know the pain of having to redeploy after each .xhtml file change to see the changes, even if they are only cosmetic. I wrote about possible solutions for that problem earlier, but they didn’t quite work for facelets (more specifically, templates didn’t get refreshed and any included pages).
Of course, the best solution is to try JBoss Tools and Red Hat Developer Studio. However if you want to use IDEA, or some other IDE (vi?
), try the following.
Read the full post here.
Believe me or not, but we thank the mysterious powers of the Universe for Ulrich Drepper every day. Don’t you? At least, you do if you use glibc. And you probably do. Uli has recently shown his deft style at touching both ends of the spectrum of programmers (newbies to oldsters) with a video series on Red Hat Magazine for those of us still grasping the details of a memory stack or needing a cluestick to remember to pay attention to the basics and the lessons learned.
We were seriously scooped recently when the venerated LWN began publishing a seven part series from Uli. Called What every programmer should know about memory, it is a thorough grounding in memory dynamics on modern hardware running Linux.
» Read more
In this video series on Red Hat Magazine, GNU C Library maintainer Ulrich Drepper presents information that every programmer should know. The kind of back to basics that everyone can benefit from.
Uli Drepper part 2: Buffer overflow and libc attacks
Uli Drepper part 3: Memory allocation errors
Uli Drepper part 5: Preventing exploits
This tip article has been edited and republished from the original source.
by Michael Juntao Yuan
LAMP and Java EE are two important middleware stacks for developing web applications. LAMP stands for Linux, Apache, MySQL, and PHP. They are all open source software included in Red Hat Enterprise Linux system. Java EE stands for Java Enterprise Edition. Red Hat chooses the open source JBoss Application Server (JBoss AS), which is an implementation of Java EE, as its official middleware stack.
This article was edited and republished from the original source.
by Andrew C. Oliver
At JBoss, I was asked to help write some training materials for “performance tuning JBoss/Java on RHEL/Linux”. It wasn’t a very easy task because I knew the audience would primarily be composed of administrators who might not be interested in the whole system, compounded with the fact that most people mean performance and scalability when they say performance. What I would do to make one single client connect and perform its operations as quickly as possible on a single server is inherently very different from what I’d do for 10000 users connecting to a cluster. The type of performance tuning that I do for an application with no users and all messaging is very different from what I do for a standard web application-type system.
This tip article has been edited and republished from its original location.
by Jeff Johnston
