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 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 been unable to find benchmarks for
read/write access times for really large files, and when I have the
time I will have to devote some of it to testing; however, under the
advice of a good friend, I will need to get the little things working
before I optimize the storage during operation.
With regard to what I am doing... I don't want to spout vapor about an
app barely started; yet, as I said it's an editor, but the resultant
data, after manipulation of the original data, can't be placed in the
browser cache, and that's the reason I was and still am wondering if
shared objects can come to the rescue.
Ktu wrote:
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 30, 2009 at 3:39 AM, Anthony Pace
<anthony.p...@utoronto.ca>wrote:
-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 set the storage capacity to unlimited?
-Has anyone clocked speed of read and write access when files get
extremely
large?
-Has anyone come up with a better solution when the app has to run
in the
browser?
I worked with shared objects a while back; however, I never really
needed
to use them to store much more than cookie data. I am thinking
about asking
the user to set the local storage to unlimited, in an attempt to
decrease
the amount of memory that is required by an application, especially
when it
gets to the 40mb or more of dynamically generated content and the
user has
limited memory on their system. The user needs to be able to load
multiple
files to be modified, and the modifications could be rather intense
and have
very large file sizes; yet, not all files and resultant data will be
required for modification at the same time, and I was hoping that
storage on
the system as a shared object, would be able to act as a scratch file.
I know this isn't new, but I was also thinking that if the file is used
properly, and storage is set to unlimited, one could make an
application
with most of the interface elements stored in the shared object;
therefore,
even if the user clears their cache, the swf can check the shared
object to
see when it was last updated and reuse what's stored if nothing has
changed.
(reducing bandwidth and download time requirements)... Is this a pipe
dream?
_______________________________________________
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
_______________________________________________
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
_______________________________________________
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
_______________________________________________
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
