I just found out yesterday that the proposal my co-worker and I submitted for RailsConf 2007 was accepted! Quite exciting. I hope to say more later, but for the moment, the talk will be about using Rails and Adobe's new Apollo technology.
02 February 2007
Subscribe to:
Post Comments (Atom)
DealBase.com
4 comments:
Hope to hear something good about WebORB rather than that annoying HTTP-based Flex/Ruby integration Adobe keeps shoving down developer throats.
I don't know if we will be doing WebORB. It depends on your goal as to whether that is applicable/usable. In most of our work, we need to have our web services work with more than just ActionScript/Flex, so generally use a REST web service API. There are examples of WebORB in the Ruby on Rails Flex SDK though. If we do not use it (and/or if we do), I will try to ensure we discuss when/when not to use it, etc.
Chris, how can you talk on the subject of Apollo/Ruby integration and not use WebORB? I think it will look completely retarded to use those silly HTTP GET/POST requests over pure AMF3 remoting which WebORB for Rails nicely implements. I wonder if there's any Adobe politics (and/or money) got involved here.
I disagree. WebORB ONLY works if you are doing pure Rails + Flex/Apollo. Yes, this talk is on those two technologies, partly because it's at RailsConf. But, you are then boxed in. You cannot then expose your web services API for other, non-Flex/AS components, without essentially implementing a second mechanism.
Adobe has no involvement in this talk, aside from the fact that we work there, and use these technologies. From the discussions I've seen so far, the suggested use of either approach is, to use WebORB if you are primarily building a Flex application, where the backend is a smaller portion of the effort and you have no other external needs; and to use a REST web service API if you have a significant server-side infrastructure, and the Flex or Apollo client is just one piece of your system.
As in all these technology decisions it is a case of choosing the right tool for the situation. At this point in our project, the right tool is REST web services because we are exposing the API to more than just an Apollo client, and do not want to do two implementations.
Post a Comment