Storage is the best option for interprocess communications if you want to use
preemptive processes. I have not done any real benchmarking but I have not
noticed that anything seems slow. By setting up return values on a per-process
basis you can avoid locking contention on storage.
For
OK i have done this many times with a table. You have multiple records in the
table, one for each id you need. I usually make that records key name
([table]field). If you have to keep track of released numbers, you can add a
blob field. I would not be adding object fields as you can not access
Humm... interesting comment. Why do you say Storage is slower and can produce
deadlocks? Tell us why you believe this.
Was my example an example of “not well programmed”? Be honest. Give me real,
solid, constructive criticism. This is a forum for exchanging ideas and
learning. I’ve been
I totally agree with Christian, in fact,
the point (slow, should be avoided if possible) was right there in the Summit
keynote.
on the point of "slow"
of course it is a relative thing and perhaps not a big deal depending on the
context,
but you only have to run code with Storage and the speed
> But lets explore other possibilities.
Hopefully not. You should avoid Storage where you can. They are slower and can
produce (if not well programmed) dead locks.
--
Grüße/Regards,
[heubach-media] | Christian Sakowski
christian.sakow...@heubach-media.de
iChat/AIM: SakowskiF
Tel: +49/(0)40/52
I really want to place a bunch of our code / forms into a component. It will
make it much easier to install into other systems, and to update that code /
forms as into older designed system that use an older version of the component.
Of course it also protects what could otherwise be
6 matches
Mail list logo
