Just that I'd like to help on this - specifically the DMBS integration,
which you know but others may not =) How about in addition to Transform
state (t,r,s) we also store material state (r,g,b,trans) for those people
who like to animate those things (trans is a big one since it can be "not
there" with a trans of zero, particularly since some browsers do not
include anything with o trans as a factor in collision detection...I see
manipulatable maze games as a demo...) THis is often much easier than
using EAI to add/remove objects from the scene, and you can animate it to
get a "fade in/out of reality" effect which is neat to show layers or
parts being added/subtracted (there is a small non-persistent demo of this
on my site).
Just some quick thoughts, we can do more/less depending on time =) Talk
to you soon jeffs...Nov 6th and 7th I'll be presenting at Oworld/Db3 in
San Jose if anyone would like to chat...
-Andy
Andrew Phelps
Department of Information Technology
Rochester Institute of Technology
http://www..it.rit.edu/
http://andysgi.rit.edu/
>
> as a first step
> I figure I'll package up the server-side code
> and convert some things from jdk1.02 to jdk1.1.x
> then add simple persistence for username/password/TransformState
> using JDBC to keep stuff in a DBMS...
>
> anyone got any comments? suggestions?
>
> jeffs
>
