I've decided to continue work on the remote drupal entity module I was hacking on when joachim pointed me this module in the first place.

It seems like to would make sense for it to depend on this one, and I have a question.

How should we namespace the modules?

The existing module prefixes with "clients", clients_ms_dynamics_soap, and I'm not sure that makes as much sense as something like "remote_entity_drupal"?

Not saying that the existing module should be renamed, but I wanted to bring this up before I open a sandbox with my code and name it something "bad".

Comments

joachim’s picture

joachim commented

The clients_ms_dynamics_soap module is prefixed with 'clients' because it's a connection type for http://drupal.org/project/clients. It works with Remote Entity, but you can actually also use it standalone, and make your own direct requests to the MS Dynamics Server.

So if your module provides a Clients connection type, I'd prefix it with 'clients'. Though that does mean it should aspire to be a generic connection -- keep a split between the connection class, and the resource class which provides the remote entity stuff.

If on the other hand you're doing something which extends Remote Entity API, then prefix it with 'remote_entity'. In that case, your module should (probably!) not care about what the underlying connection type is.

joachim’s picture

joachim commented
Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Anonymous’s picture

(not verified) commented
Issue summary: View changes

Add reference link