On Aug 26, 2018, at 2:00 PM, Keisuke Miyako wrote:
> 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 difference is quite
> palpable.
> it is not a 4D specific phenomena, it is intrinsic to how blocking based on
> mutex works.
>
> on the point of "good coding"
> 4D forces you to forfeit exclusive access with the "Use/End use" code block,
> so unless you implicitly use storage in a stacked subroutine (super bad idea),
> it is hard to violate the FILO tule unintentionally.
>
> a more subtle gotcha is to make the mistake of
> using objects and collections as if they were values, not references.
> it's not limited to storage, but it can really bite you when you make the
> mistake with storage.
Good to know. John and my idea of using storage for sequence numbering is a bad
idea. That’s why I posted here to get comments on if it was a good idea, or a
bad idea. Now I know it’s a bad idea.
Storage is slow, so avoid using it if you can. But if you need it, it’s there
to be used as a tool. But only in certain circumstances.
I’ll watch and see what others do with storage to learn when it is a good thing
to use.
Tim
Tim Nevels
[email protected] <mailto:[email protected]>
Innovative Solutions
785-749-3444
**********************************************************************
4D Internet Users Group (4D iNUG)
Archive: http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub: mailto:[email protected]
**********************************************************************
