🚀 go-pugleaf

Kevin,

I expect to face a similar dilema in a few weeks. Have not done much work in
the area yet, but the implementation we're considering involves a dedicated
table in our server database. Basically an application metadata table
implementation of the old Windows .ini file. In our case, we're hoping to get
away with textual and numeric data only, rather than serializing the
application objects.

Kevin D wrote:

> What would be the preferred method for saving state info for a Java
> application?
> i.e. form position & size, column sizes within grids, Sort Order within
> grids, current form, etc.
>
> I want this info to follow me from PC to PC and to be platform independent.
>
> Would cookies do the job, a property file saved to a server,
> or a serialized class saved as a blob in a database??
>
> Any ideas.
>
> KD