RE: [Webware-discuss] serving XML to a Java applet with webware

[Geoffrey T. <gta...@na...>]

Adam Gent wrote:
> Here is why sessions might be a problem. Lets say that
> I have page A, page B and page C (all input pages). B
> and C are input a new item or choose an existing item.
> Page A needs input from page B to be submitted and
> page B may need input from A to be submitted but
> definatly needs input from page C.  Page C may or may
> not need input from page A.   So if the user goes to
> page A and enters some information and then goes to
> page B he might go to A to enter new information which
> will wipe out the old information for A in the
> session. (This database is linked up all over the
> place). So the only solution I had for awhile besides
> using a ton of logic an field variables was javascript
> windows...obviosly not a clean solution.

I'm afraid I don't understand the problem.  What does "he might go to A to
enter new information which will wipe out the old information for A in the
session" mean?  Visiting page A will only wipe out session data if you
choose to write your application that way.

It almost sounds like you're implying that session data is somehow tied to a
particular page.  That's not true.

- Geoff