Thanks, Alex, but in earlier years, the adapter class inherited from SourceAdapter, now it inherits from Rhoconnect::Model::Base Is there any changes in the code we write for the source adapter as a result of this? Any caveats?
Thanks, Alex. I noted this in particular, which indicates a good change from the earlier RC :
In previous versions, a Source Adapter consisted only of one class – which is now has been moved to Source Adapter model. “Controller” part of the Source Adapter has been hidden inside of the RhoConnect library code. This posed a significant obstacle in a way how the developer could utilize the code and the common techniques. To overcome this obstacle, RhoConnect 4 provides you with direct access to the Controller allowing you to customize route behavior and utilize all of the powerful sinatra plugins/extensions that are available.