web services - Are there best practices for naming SOAP interface methods and variables? -
web services - Are there best practices for naming SOAP interface methods and variables? -
in .net, microsoft has guidelines naming classes, members, etc. when developing class libraries. other languages may have best practices how name classes, how/if utilize notations.
now soap protocol can used perchance communicate across language boundaries. there best practices how name functions, variable names, etc.? or should utilize whatever language (if @ all) uses? or when i'm generating soap interface via tools (e.g. wcf service contracts), should utilize whatever tool produces?
there seems no official w3c naming convention service method names.
some commonly used guidelines:
method names should indicate client's point of view
use different method names instead of overloading
in general, pascalcasing seems favored (no underscores). .net, follow .net naming conventions normal methods.
you may find this blog post oracle useful.
web-services soap naming naming-conventions
Comments
Post a Comment