the more it changes

More thoughts on restructuring the jar files. I'd like to keep the jar files "pure", so there are not a lot of inapplicable classes in a jar file when you go to use it. Smaller jar files should make it easier to find things too, if there is a good top-level structure.

First, I'm thinking that each portal and each client should be in its own jar file--typically I suspect that you would only be using only one portal in a server. So the direct portal should have its own jar file. One complication here is that direct is also a client, so code common to direct and a text client should again be in a separate jar. And I already have two such classes for handling the entry of passwords.

So the current code then gets reorganized into 4 jars:

1. Ark,
2. Framework,
3. Common text client classes and
4. direct text portal.

And the current main then gets moved to the last jar file. But note that common portal classes would remain in the framework jar.

Its a bit more structure than I had previously envisioned, but it should help keep things well organized. And that's important, as I expect this all to grow considerably.

Bill