Re: [Flashcoders] shared objects as a sort of scratch disk file

2009-10-03 Thread Anthony Pace
As an example, any type of multi or large doc editor would benefit; especially on a system that has little memory. Storing assets for the interface is most definitely an option without asking the user, if the data is vector based; yet, for bitmap data, I would have to ask the user. I have

Re: [Flashcoders] shared objects as a sort of scratch disk file

2009-10-03 Thread Paul Andrews
Anthony Pace wrote: As an example, any type of multi or large doc editor would benefit; especially on a system that has little memory. Storing assets for the interface is most definitely an option without asking the user, if the data is vector based; yet, for bitmap data, I would have to ask

Re: [Flashcoders] shared objects as a sort of scratch disk file

2009-10-03 Thread Latcho
What is a large doc ? What is little user memory if we talk gigabytes these days and the LSO has a default limit of around 100Kb ? This is a no no from flashcoders pro :) Anthony Pace wrote: As an example, any type of multi or large doc editor would benefit; especially on a system that has

Re: [Flashcoders] shared objects as a sort of scratch disk file

2009-10-02 Thread Ktu
I like the sound of that. It certainly seems like something someone should look into. I'm not great with checking speed in code, but I want to try to look into that. I'm interested in what types of applications would benefit from it. Can you share anything about yours? Ktu [k-two] On Wed, Sep

[Flashcoders] shared objects as a sort of scratch disk file

2009-09-30 Thread Anthony Pace
-Now, if the user sets the local storage amount to unlimited, it is possible to save and modify heaps of data; yet, at what cost speed wise? -Is there a max size to a shared object, even if the user selects unlimited? -Is there something wrong with my idea, other than having to ask the user to