Re: What are com.blah or org.blah?
Chris Uppal wrote:
It makes no difference how you name your packages if they are only used within
your own organisation (living room, whatever). The only constraint is that
you avoid "inbound" clashes (as it were) which you can do by, say, putting all
your stuff under "local" (local.mystuff.whatever) since "local" isn't a TLD and
is unlikely to become one. If, on the other hand, you /do/ want to make your
code more generally available then you almost certainly are going to put it
somewhere with an associated global URL -- in which case you can use that for
the root of the package names.
Then you get into the problem of ensuring that that URL continues to
belong to your software for as long as the software remains in use. It's
very hard to get any kind of stable Web hosting at all on a budget
nowadays ("stable" as in "url doesn't change -- ever"). Probably you
also want the javadocs to be hosted stably for others to link to.
Why isn't there a good, free Web host these days, let alone one with
staying power that doesn't rearrange things internally on its own? It
seems you're artificially constrained to three options -- keep your
software entirely private, use an existing open source hosting site like
SourceForge, or go commercial *and be successful*. Anything else means
paying for hosting out of your own pocket, *on top* of whatever you
already pay for network access (shouldn't hosting of at least a small to
medium amount of data at a stable address be included as basic network
access? But it's not...) and that means you'll be paying to keep your
Java online and legitimate for a lifetime (its or yours).
So much for "free", even as in beer...