Hi,

I noticed a move away from method names matching function names (e.g. node.load has become node.get). I guess this makes sense in a way, to have a common language for services, but I found it more intuitive to expect the Drupal function name, for example, views.get could be views.embedView.

Perhaps this is a terrible idea. I stand ready to be flamed. Just putting it out there. ;-)

Comments

marcingy’s picture

Status: Active » Closed (won't fix)
greg.harvey’s picture

I guess that's a "no" then. ;-)

marcingy’s picture

Status: Closed (won't fix) » Postponed

Actually on second thoughts i'm going to set it to postponed - I'll discuss this matter with the rest of the services team at Drupalcon, so as we can define how this will work going forwards.

greg.harvey’s picture

Cool - I'm sure the team decision will be sensible, whatever it may be.

marcingy’s picture

Priority: Normal » Minor
Status: Postponed » Active

After discussion yes we should use this approach. Low priority for now.

greg.harvey’s picture

Great, thanks for the feedback. =)

nonsie’s picture

Perhaps this bit should be on the project page/somewhere in the handbook so that people writing patches/new services could be aware of this?

marcingy’s picture

Good idea - http://drupal.org/node/406868 has been added.

gdd’s picture

Status: Active » Closed (won't fix)

So I'm not going to go back and change all the existing functions, it's just too big a deal to do for the module given its wide usage. I also have no idea what the services will look like in any redesign. In principle I agree with the spirit of this issue though, and will keep it front of mind in future design.

All that said, marking this won't fix.

greg.harvey’s picture

Thanks for the update. Appreciate the issue. Services wasn't too widely used when the issue was initially raised, but I guess Pandora's box is open now! =/