On Jul 16, 1:48 pm, Robert Klemme <shortcut...@googlemail.com> wrote:
On 15.07.2011 18:38, Ross wrote:
Fundamentally the program I'm writing is an experimental program,
rather than a commercial product. Hence, my primary aim is to get a
working version of it that I can release to people, and see if they
like using it. If it's a hit, then it's reasonable to start rewriting
bits of it to make them more elegant under the hood. Otherwise, if th=
not enough to "start rewriting bits of it" but you need to rearchitect
it which often means a major effort.
Experience shows that code that exists has a certain - err ductility? -
which keeps it hanging around longer than you may want.
If you are afraid of the learning curve you could at least replace your
custom format (which we do not know) with something like JSON which is
pretty short yet allows for arbitrary structured data much like the
verbose XML. That will give you flexibility and avoid having to fidd=
with the details of parsing.
I wouldn't say that I'm "afraid" of the learning curve, just that I
would
rather allocate the time to other things. The client/server part is an
add-on
to my current application, rather than a major part of it. And, the
code I have
is reasonably simple, and it works, which is what I want. I don't
believe that
I'll need to rewrite it ever if I don't want to.
I'm going to write another client application soon, which will have
very limited
communication between the client and server. So, what can I use that I
can distribute
as an executable .jar file that doesn't require any other resources
such as SSL
key files, doesn't require policy files, or the rmiregistry to be
running, etc?
Sometimes you just want to "do it" rather than spend a month in
analysis paralysis.
Also there's the age old saying "plan to throw one away, you will
anyway".