Proposed Hessian Extension For Erlang
In a lead up series of articles, I discussed the motivation and protocol flow of an extension to the Hessian web services protocol. This installment outlines the first implementation of the proposed protocol written in Erlang. This article assumes knowledge of the Erlang programming language and the Hessian serialization protocol in order to run the examples. For those that are primarily interested in Hessian and not Erlang, this article is tractable to the extent that you can read over the Erlang specifics.
Post a Comment
AS3 AMQP Client: First Cut
Updated on Tuesday, April 1, 2008 at 05:39PM by
0x6e6562
In a previous article I introduced a proof-of-concept client for AMQP written in AS3, which at the time had not been released as a formal artifact. The proof-of-concept implementation has now been refactored and cleaned up in order to release it formally. The article announces the first release of this library and describes its usage.
2 References
Camel Case
Recently I had to convert delimited String tokens into CamelCase Strings in Java. The input was something like "foo-bar" and the output should be "FooBar". A little googling found the TreeBind library, which does exactly that. An example of the API usage looks like this:
Util.ToUpperCamelCase("foo-bar"); // returns "FooBar"
Util.ToFirstUpper("foobar") // returns "Foobar"
Not rocket science, but it did save me some string manipulation. BTW, I don't even know what the TreeBind API does in general.
Hessian Type Negotiation: Protocol Flow
In a previous installment I discussed the motivation behind an extension to the Hessian binary web services protocol. That article demonstrated the efficiency gain of adding explicit type negotiation to the protocol. The goal of this article is to have a deeper look into this extension from a protocol flow perspective.
Type Negotiation In Hessian
Updated on Monday, March 3, 2008 at 10:38PM by
0x6e6562
This article discusses the motivation behind a type negotiation extension to the Hessian binary web services protocol. The goal of this optional extension is to optimize the handling of type information in terms of network overhead, processing overhead and type mapping in non-reflective languages. This extension has been implemented on top of the Caucho Java Hessian implementation. This article contains a preliminary benchmark and links to download the source of the extension.
