> as a start
> I am probably going to port the server code
> to the JDK 1.1.something
> so that I can add a JDBC-based "middleware" module
>
luckily, no porting is needed: it runs and compiles under 1.1
as is. actually, you can use the 1.1 compiler
and it will run just fine under 1.0 (as long as you
avoid any new 1.1 constructs...)
> I wanted to ask the vnet-interest list for some input
> on what should persist and what should not
> so please take this as a general call for discussion
> about the issue of persistence in MU settings...
> I would like to "think out loud" with folks
> about such things as
>
> whether the next logon should restore the last transform state
> whether users should be able to designate a default avatar
> etc etc
persistence doesn't really become critical until you
start talking shared objects. is that what you had in mind,
or do you mean taking the current code as-is? if you just
mean the current code, and just want to persist some
preferences, you might want to consider skipping jdbc and
just using java.util.Properties into regular old text
files. it's simple, free, reliable, and very portable.
-cks
