No, it wouldn't work for AR. And, its not because of the read only nature of DAAP. The real issue is that DAAP is deceptively named. DAAP is not really the database itself, but a service allowing you to get information about an internal music database. Daap is not a reusable database for mulitple database configurations. Basically it goes only as far as "what songs do you have?" and "can i hear one?" that's the connection information passed and delt with.

ActiveRecord is meant for versitile databases to make them easier to work with. It would be rather pointless to create a layer for DAAP as its structured and would require a model for each structured data type.

Since there is a gem for DAAP it would be trivial to use that object within a project and actively use the DAAP connection during your webserver existance. (I'm not saying it would be fast.)

-hampton.

On 5/25/06, Jeroen Janssen <[EMAIL PROTECTED]> wrote:
Hi,

I was wondering if anyone has worked on a Active Record Connection
Adapter for DAAP yet (possibly using the daapclient gem).

If not, any indication on how difficult it is to write a connection
adapter (I'm fairly new to ruby and rails, but I have a fair amount of
programming experience)?

As far as I currently see, the 'connection' would be readonly, is that
a problem for AR?

Best regards,

Jeroen Janssen
_______________________________________________
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-core

_______________________________________________
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-core

Reply via email to