Let's imagine that EJBs, CORBA, or any RPC protocol was implemented in a library in a way that the user is responsible for i.e. marshalling its content:
result = MyLibrary.send("header content", 1287361278361278365674)
if result==200
order_price = result.body[95..100]
else
raise "unable to retrieve order information"
end
What hapenned? Is it really an EJB/Corba/RPC implementation if you have to marshal/unmarshal on your own? Or is it just a socket …
- Alexey Kovyrin's Blog: Rails Developer for a Large Startup: My Vision of an Ideal Candidate
- processi: ruote 2.1 released
- Me Dev, You Jane: Contact List using SproutCore, Mochiweb and Mnesia
- blog.webandy.com | Andy Atkinson: WindyCityRails 2009 conference
- Stake Ventures Inc.: OpenTransact a tiny payment standard
- Trevor Turk: Weekly Digest, 8-10-09
…Tradicional web services decouple a little bit more than traditional RPC, but still provide this amount of coupling that cost our companies more than they were expecting to pay .
The entire video cast on the 3rd part from Rest from scratch is here:
This code achieves its results using Restfulie 0.8.0, with many thanks to everyone who contributed …
- Rizwan Reza: Revamped Routes in Rails 3
- English - AkitaOnRails.com: Chatting with Adam Jacob
- World Wide Webber: InfoQ Virtual Training
- Mike Clark : iPhone on Rails
- Litany Against Fear: RESTful Possibilities - REST in Rails and Beyond Notes
- DevInterface Blog: The top 20 plugins to create a Rails application
Avro RPC support : currently Cassandra's client layer is the Thrift RPC framework, which sucks for reasons outside our scope here. We're moving to Avro, the new hotness from Doug Cutting (creator of Lucene and Hadoop, you may have heard of those). Basically this means porting org.apache.cassandra.thrift.CassandraServer to org.apache.cassandra.avro.CassandraServer; some examples are already done by Eric Evans.
Session-level consistency : In one and …
- High Scalability: Hot Scalability Links for February 24, 2010
- Mike Perham: Cassandra and EventMachine
- Viget Extend : The Development Lab: Database Taxonomy
- Blue Box Group: News: NoSQL Meetup at Blue Box Group
- Ruby News: Red Dirt RubyConf 2010
- James on Software: Opinionated Modular Code
The RPC piece of Avro is also pretty straight forward: the protocol is defined as an Avro schema, where both the inputs and the methods (along side with the request / response input and output parameters) are provided inline. In principle, this also means that given the right framework, different clients could easily negotiate different data-formatting on the fly, without having to worry about versioning or conditional code paths. A simple Mail protocol with …
…in JavaScript and all Object-oriented programming languages. It's RPC and object-oriented.
REST Model. The "Web programming model" as Google calls it. This is less of an API and more of a protocol(s). It's resource-oriented or document-oriented.
Comet model. Asynchronous programming model. Data is passed through several message channels. Everybody are clients, they can publish and subscribe to the channels.
I have been somewhat obsessed by this quest since …
… Team spoke about BERT (for Binary ERlang Term) and the RPC protocol and server he built with it. The talk had great information about the specification for BERT and the protocol but, it also had a message of experimentation, with some of Tom's guidelines, tacked on. I'm not sure if this approach was effective. His message encouraging rubyists to experiment came across as pontification, in many ways. I hope attendees were generally able to move past this to absorb the quality …
- Ruby-coloured glasses: Rails underground
- Matthew Bass: Secrets of Nomadic Programming
- Rubycon - All things geared towards web development: Jim Weirich - Test Driven Development meets Design by Contract
- Alex Young: Fear and Loathing in JavaScript DSLs
- Scottish Ruby Conference: Call for papers coming soon
- Ruby Best Practices: Fun with Class.new
…only that, but you're using Thrift for cross-language, high-performance RPC support. Nothing but the latest and greatest for you, eh?
Out of the box, though, sbt knows nothing about Thrift. Fortunately, it's easy to wire that up. You just want to throw something like this in your build file (you know, the one in project/build that you created while following along with the superb documentation that sbt offers?):
1 2 3 4 5 6 7 8 9 10 11 12
lazy val thrift = task …
Building Thrift Dependencies In Scala with sbt
So you're using the fantastic simple-build-tool (sbt) to build your Scala project. Not only that, but you're using Thrift for cross-language, high-performance RPC support. Nothing but the latest and greatest for you, eh?
Out of the box, though, sbt knows nothing about Thrift. Fortunately, it's easy to wire that up. You just want to throw something like this in your build file (you know, the one in project/build …
- Khaled alHabache's official blog: Scala is my next choice
- saladwithsteve: Alex's Scala Talk at C4[2]
- PaulBarry.com: Infinite Recursion
- Ruby, Javascript, Erlang blog: Snakes, Gems & Coffee: The Scala vs Erlang Debate, Part 2: The Geek Off
- Headius: The Future: Part One
It's interesting working with clients who are passionate about URL structure.
Introducing BERT and BERT-RPC - GitHub's new binary data serialization and RPC protocol. They may have invented the ruby of RPC.
Devise: flexible authentication solution for Rails - Built on top of Warden. I'm not personally sold on pushing authentication down into Rack, but if you are this engine is probably worth a look.
Pimping out git log - An alias to get nicer command line displays.
- Travis Dunn: Web Service API Design By Example
- saladwithsteve: My first Thrift app
- Robert C. Martin's Weblog: Web Services? What has the industry been smoking?
- Riding Rails - home: Community Highlights
- Rails Inside: Devise: Flexible Authentication for Pragmatic Rails Developers
- Plataforma Tecnologia Blog: Devise: authentication for lazy programmers
Positive: eBay is firmly in the RPC design camp, and frankly, aside from desirable auction data, there's not much to recommend the API. If the documentation seems exhaustive - and it most certainly is, see the guide to REST , for example - then it's an honest emmisary of the beast of a system which sits behind an ostensibly friendly API frontend. Although there are detailed code samples and a development sandbox , these are more necessary complications …
- John Barnette: Versioning HTTP APIs
- The messagepub Blog: Litmus uses messagepub for IM notifications
- Rails on the Run - Home: db fixtures replacement solution step by step
- Developing with Style: Cake Nibbles #4
- A Fresh Cup: Double Shot #548
- Viget Extend : The Development Lab: Provisional: New And Improved!