Ok, but Preferences was a Pivot version of Java Preferences (a Map of <String, String>), with a default format of json, and standard placement in the storage (user home in the case of File System, or Web Start storage for Web Start deploy).
Right, but we eliminated that class because it didn't seem like it would offer enough value. Again, if you create a demo that shows how to use JNLP persistence in a Pivot app, developers can use that information to create their own preferences classes.
I don't like too much things like "SimplePersistence" ... Do you have some idea instead ?
It's your demo, so it's really up to you. To me, that sounds like you are trying to create a general-purpose, re-usable class. I'm not sure that's necessary, because I think the JNLP APIs already provide that for us.
If I were building it, I would start by creating an app that simply demonstrates how a basic Pivot app can take advantage of JNLP persistence. If some re-usable code happens to come out of it, that would be great.
