The App Server and the CRB

[Ben Butler]

Hi Bas

I would create an object reference to hold (each thread) that would hold
the associated data for that thread's data. Or store the object refs in a
list in a file only memory format.  Then I can call these's refs to get or
set any data I want to i/o with the specific instance of the remote thead
and use another column as a session ref.  Then we can decouple persistent
session data from the thread handling as needed

Ben

On Sat, 20 Jun 2020, 22:35 Das Goravani, <das at goravani.com> wrote:

>
> Hello
>
> I’m trying to understand the difference between the CRB and using rows to
> hold data in the App Server.
>
> Say you have a chunk of code, big, that does one thing.. in my case an
> astrological chart and readings.. then another big chunk of code and
> reports that creates a PDF output.  You want these online.. using the App
> Server.. so that people can get astrological reports.
>
> Using the App Server.. say one persons code is running.. and their time
> slice ends.. the next person in the que starts to run and overwrites the
> values in the CRB with new ones.. bad.. I’m led to believe presently that
> is what happens.. that the CRB is shared between users..
>
> And people said therefore you have to use ROWS and reference them rather
> than fields from file formats.. but rows and lists are ALSO in the CRB and
> subject to being written over aren’t they?
>
> Or is it that what’s meant is to use an object for all your code.. and
> variables.. and then OBJECTS INSTANTIATE FOR EACH USER????
>
> Do they?
>
> How do you get your rows and lists to NOT be overwritten just as the CRB
> is.. ???
>
> If you widen the time slice so that there’s enough time for it to finish
> the part that is in the CRB do you think that is viable as a way?
>
> It would be a really huge task to convert all my code in those two chunks
> to being all rows and lists holding data and references to them in all
> code..
>
> I’m thinking of putting my astrology readings online.. thinking of using
> the app server.. if I kick off users that hasn’t budged in 5 minutes maybe
> I can keep the number of users down.. and affordable.. the unlimited users
> price tag is a bit high for me at like 14 K … wish I could do it.. then I
> wouldn’t have to kick off users..
>
> This note is about how does rows do better than the CRB in terms of
> keeping users data separate on the app server.. that is really the
> question..
>
> Das
> _____________________________________________________________
> Manage your list subscriptions at http://lists.omnis-dev.com
> Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com
>