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
Comment #1
marcingy commentedComment #2
greg.harveyI guess that's a "no" then. ;-)
Comment #3
marcingy commentedActually 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.
Comment #4
greg.harveyCool - I'm sure the team decision will be sensible, whatever it may be.
Comment #5
marcingy commentedAfter discussion yes we should use this approach. Low priority for now.
Comment #6
greg.harveyGreat, thanks for the feedback. =)
Comment #7
nonsiePerhaps this bit should be on the project page/somewhere in the handbook so that people writing patches/new services could be aware of this?
Comment #8
marcingy commentedGood idea - http://drupal.org/node/406868 has been added.
Comment #9
gddSo 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.
Comment #10
greg.harveyThanks 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! =/