Re: Style question: SOAP method naming.

I think being consistent is best. I personally find it annoying to have both naming conventions mixed in code, if they are used in the same domain of usage. So, look at boundaries. I'd use underscore_style in private code, and (maybe) camelCaseStyle for things consumers of the web services may see. Where both of them overlap, maybe a s/((?<!^)[A-Z])/'_'.lc($1)/ge (and it's reverse) would be handy for method translation... ;-)

--shmem

_($_=" "x(1<<5)."?\n".q·/)Oo.  G°\        /
                              /\_¯/(q    /
----------------------------  \__(m.====·.(_("always off the crowd"))."·
");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}

Comment on Re: Style question: SOAP method naming. Select or Download Code

Replies are listed 'Best First'.
Re^2: Style question: SOAP method naming. by duckyd (Hermit) on Aug 23, 2006 at 06:11 UTC
I'd second this recommendation. Camel case is standard for web services, and I'd use it for all SOAP methods exposed to the user. I'd use underscore_style in your code, per Perl convention. As annoying as it may be to have both styles around, it will help distinguish what's exposed to the user and what's not, and will keep your external interface in line with what SOAP users expect, and your internal code in line with what Perl people expect.	[reply]

Replies are listed 'Best First'.

Re^2: Style question: SOAP method naming.
by duckyd (Hermit) on Aug 23, 2006 at 06:11 UTC

I'd second this recommendation. Camel case is standard for web services, and I'd use it for all SOAP methods exposed to the user. I'd use underscore_style in your code, per Perl convention. As annoying as it may be to have both styles around, it will help distinguish what's exposed to the user and what's not, and will keep your external interface in line with what SOAP users expect, and your internal code in line with what Perl people expect.

[reply]