>
> New root namespaces are not necessarily a bad thing. Individual modules
> with top-level names are discouraged, but e.g. VMware::LabManager would
> be just fine.
>
Ah, I misunderstood that guideline for creating root Namespace. Thanks
for clarifying it.
--aditya
# from Aditya Ivaturi
# on Thursday 04 February 2010 01:39:
>WWW::... since it is actually going to use HTTP.
It doesn't talk to a single public service hosted on the World Wide Web,
so WWW is counter-descriptive.
>This way, we don't end up with a new root namespace.
New root namespaces are n
Subject: Namespace discussion - VMware::LM
I already submitted a request to register the namespace VMware::LM for
a new module I am writing. This module is an interface to the VMware
Lab Manager SOAP API -
http://www.vmware.com/pdf/lm40_soap_api_guide.pdf.
But when I think about it more, WWW::VMware
> Since its a special case of SOAP the SOAP should go before VMWare IMHO.
> Also it sounds like a network protocol thing rather than a www thing. www
> implies html not just http. SOAP uses XML.
>
Sounds reasonable. So since I already submitted a request for
VMware::LM, will it just be ignored? O
I already submitted a request to register the namespace VMware::LM for
a new module I am writing. This module is an interface to the VMware
Lab Manager SOAP API -
http://www.vmware.com/pdf/lm40_soap_api_guide.pdf.
But when I think about it more, WWW::VMware::LM seems to more
appropriate namespace
