Hi everyone Not something urgent, but something to think about. I suggest we make ActiveSupport a dependency of ruote, especially with a view on the upcoming ActiveSupport 3 that aims to be lighter and more modular.
This can be greatly beneficial for serializing data to/from JSON & XML. ActiveSupport 2.3 has pluggable XML-backend support so engine users can use REXML, libxml-ruby or nokogiri for processing XML. On the current rails-2-3 stable branch they've introduced the same for JSON backends [1], allowing use of the performent JSON gem or the new ruby-yjal library [2]. Even if you hate Rails, ActiveSupport is a great gem to work with, at least in my opinion. Currently the engine has some patchy support for both ActiveSupport (when available) and the JSON gem as a fallback. I think this scenario can be greatly simplified by using ActiveSupport. That said, I have no idea how everyone is using the engine and if ActiveSupport will compliment those environments. What are your thoughts? Would ActiveSupport help us free the engine from some tedious serialization tasks, or would ActiveSupport ruin a perfectly good product? On my fork of ruote [3] I've already updated the Jabber participant/listener pair, the AMQP participant/listener pair and the nanite mapper participant to explicitly require and utilize ActiveSupport's JSON abilities. Kind regards 1 - http://github.com/rails/rails/commit/d052e9fb5868a10df33a84bf61f40a32df9e78ec 2 - http://github.com/brianmario/yajl-ruby/tree/master 3 - http://github.com/kennethkalmer/ruote -- Kenneth Kalmer [email protected] http://opensourcery.co.za @kennethkalmer --~--~---------~--~----~------------~-------~--~----~ you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en -~----------~----~----~----~------~----~------~--~---
