on 03-21-2006 5:38 PM
As the subject says...
The top-level namespace prefix looks very useful for segregating projects into their own namespaces...is this what this is for, or does SAP have another recommended use for this prefix?
The vendor name already makes the namespace unique to a corporate entity (if you use the domain name), so anything after that is really only of importance to the internal development environment...
If you have partners developing for you, or your development is big divided into different orgs,
the namespaces can make your life really easy distinguish the code and packages.
Regards, Angel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Even if your development isn't that big, using the 'name space prefix' would allow you to further segregate your codebase.
This also becomes important when your domain name is rather long - 15 characters. Take away four or so more for the namespace prefix, and you're left with 20 characters for the DC name. Add in a few separators, and you're down to 12-15 characters.
Obviously, readability can suffer when you start to abbreviate too much, so I'm looking for best practices when it comes to the namespace prefix.
Thanks for your comment.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.