DONE - general problem is that i need to put a value in select() else the
write doesnt register until a new connect happens.
Fixed with inputs from Ron Hitchens - this problem started with 1.4.2
(perhaps)

- test SMSSender with a dummy jsp.
- check with pipelining and the pipetest
Yes. things seem to be functioing. Need to write to files and check
exactly that nothing is being lost, and exact order is mainatained
between testchat.sh and testpc.sh.

- instead of hardcoding constants from Server, we should pass the server
  instance down, so that servers can be changed.
- the server itself could become a framework on which apps can be
  hosted. CommandHandler etc would be part of framework. Each app would
  have a Commands file. (LATER)
- pick up options from a file: close on write, close on read etc, so
  user doesnt have to hunt for where to change code.
  Also, whether SMSSender should be Pipelined or not.
  Whether a given incoming request should use pl or not. we shd not have
  2 different chat's. The Incoming class can be selected conditionally.
- which writer to use, should also be in properties.
- i dont think we need to pass Nio/selector to command, writer etc. they
  dont seem to need it. the Writer has an instance of the incoming Nio.

immediate:
request_counter increment - this pertains to only pipelining. it should
not go everywhere.
message has one extra space.
is command lowercased ?
close channel, or write back to channel.

use a pool of preparedstatements for queries
validate commands at time of registration (add a list in Commandhandler
that has all commands in it).
how to map an abbrev to a command
later - cache data of some queries and use cached data rather than sql.
    can we make this simpler to do for future.

admin requests to be handled at high priority or immediately - how to do that ?

IMPORTANT:
if we user Kannel, then the reply should/could go back in the proxy fashion
using the Proxy example. Same for any http. or should we just create a
connection - thats the dirty way which could keep threads hanging.
That should be simple, without disturbing anything, since we are not
sending back anything to SMSC over http, however what if we want to make
a pipelined outgoing connection to bulk smsc.
Proxy will currently make a separate connection each time. is our
pipelining implementation outgoing also ??