At 09:53 02.10.00 , you wrote:
>Another problem will be : cheating. Java is much easier to decompile
>than any other language, so you have to take measures at server side, to
>prevent the client from seeing things, it may not see, this will be
>quite computing intensive ...
My approach to this would be to download landscape and scenery to the
client *once*, and to heck with anyone who decompiles the data and
constructs a complete map from it. If they want to expend this much effort,
IMHO they are welcome to. On the other hand, everything dynamic, such as
the location of opponents or moveable items, should be held only on the
server and transmitted to the client only on a "need to know" basis. The
appearance of characters (i.e. their geometry and textures, etc) are an
in-between case and should be decided on a case by case basis. Maybe
download the data for a given species when the player first encounters it,
and then keep it on the client for fast access.
I'm embarrassed that we're turning the J3D discussion list into a MMOPRG
discussion list; perhaps we should branch it off to somewhere else? If
people are interested, I could put up the UBB Bulletin Board system on my
Web site, or we could set up camp in eGroups or something.
-Carl-
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA3D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
