Storage vs FileSystemStorage

[Paweł WIchrowski]

Hi,

I wanted to clarify some things about Storage. We have use case where we want to store some data on device. This data is list of objects. Those objects along with simple data (like Strings, nubmers etc.) will contain some attachments (potentially large). I should also mention that the data will be encrypted before saving and send over network. Right now we are using FileSystemStorage but we thinking about moving  data to the Storage. It will simplify development (things like lazy loading, encryption etc.) since we could operate on objects not on files. When I searched forum for some information on Storage I notice two limitation for it:

1. Whenever someone mention bigger data it was recomended to use FileSystemStorage (I remember someone talking about 20MB size data)

2. Whenever someone mention about sending that data over network it was also recomended to use FileSystemStorage

I also read about some compatibility problems with FileSystemStorage.

Could someone please clarify when we should use Storage and when FileSystemStorage?

Best regards.

[Shai Almog]

Generally Storage is far more limited in size when targeting RIM/J2ME in which case if you are dealing with more than 100kb per store I would not use storage. On other platforms storage is pretty much like filesystem.
The "unportable" portion of FileSystemStorage is the file system layout and complex attributes (e.g. hidden) if you just use the app home path to store elements in FileSystemStorage then it should be pretty portable.