Karsten wrote:
> To clarify this, you propose a solution, where if a given parameter at
> load time is set, the applet initializes itself with some default
> settings, so that it can be used without the necessity to format it?
It should be possible by delaying creation of parameter-dependent
resources as much as possible. As an example, instead of allocating
a 4kb byte array for MuscleCard objects, just leave the pointer to
null, but respond to the GetStatus command as if there were a
4kb byte array for objects. Obviously, at the very first object
creation, we would need to actually allocate the object store
and loose any possibility to change its size (unless the SC implements
the GC functionality, of course). This is true if we want to leave
the object management code at its current simplicity level, otherwise
you could even think to split objects across multiple arrays which
are created on demand.
Though, you have an issue due to Applet instantiation, instant in which
you must specify the instance size.... so, if that space is not used
anymore for MuscleCard objects, I assume you'd like to use it for some
other kind of Java objects, aren't you ? (additional keys, fingerprint
templates, .... ) .. and the Applet change is only meaningful if you
cannot (or don't want) plan at deployment-time the intended use of that
amount of memory.
bye,
Tommaso.
_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle
