Hi there!
 
    I would like to know if there is any experience/documentation about splitting
    the J3D application into the server and client-side. I would like to run the main
    processing/scene-graph updating engine, that also includes the database
    access, on the main WEB server, while only the rendering of the updated frames
    is done at the client ( in the applet). Is there a way to do that ? Does it require
    customizing the J3D source? This could also lead to multi-user sharing of the
    same database, kind of like multiplayer game, although in this case it is not a
    game, but rather database-related software. Currently (the raw prototype) of the
    software does all of the scene updates in the behavior code, including the pick-related
    actions. As those get more complicated, the frame rate would drop, unless done in the
    background. There is no problem with waiting few frames for main action to post
    the results on the screen, but the resources needed to do so may not be easily
    available on the client. Also the amount of data coming from the database would stay
    at the server side and update the scene there rather than travel across the WEB to the
    client to update the frames. Finally shared viewing of the scene would be much easier
    synchronized this way.
 
    Thanks in advance for any help!
 
    Zoran
 
 

Reply via email to