On Sun, Apr 9, 2017 at 3:46 PM, Jeffrey R. Carter wrote:
> On 04/09/2017 09:00 PM, Jeremiah Breeden wrote:
> >
> > I took a look. It looks like your entry is actually "per connection"
> unless I
> > misunderstand. Your app data structure has the serializer as part of the
> > record. Doesn't
On 04/09/2017 09:00 PM, Jeremiah Breeden wrote:
>
> I took a look. It looks like your entry is actually "per connection" unless I
> misunderstand. Your app data structure has the serializer as part of the
> record. Doesn't that mean that each connection gets their own serializer?
You're
On Sat, Apr 8, 2017 at 4:40 AM, Jeffrey R. Carter wrote:
> On 04/08/2017 03:05 AM, Jeremiah Breeden wrote:
> > I was trying to figure out how Connection_Data is handled with respect
> to Task
> > safety. In particular, if I have two Action_Event handlers and in each
> of the I
> > do something
On 04/08/2017 03:05 AM, Jeremiah Breeden wrote:
> I was trying to figure out how Connection_Data is handled with respect to
> Task
> safety. In particular, if I have two Action_Event handlers and in each of
> the I
> do something like:
>
> My_App : My_App_Access :=
Hello Jeremiah,
Even if connection "data" is stored in Gnoga protected object, that is only a
pointer as you guess right.
So it remains up to the main program to care about the concurrent access of the
data in a multitask context as Gnoga is.
HTH, Pascal.
http://blady.pagesperso-orange.fr
>
I was trying to figure out how Connection_Data is handled with respect to
Task safety. In particular, if I have two Action_Event handlers and in
each of the I do something like:
My_App : My_App_Access := My_App_Access(Object.Connection_Data);
And then proceed to use it in both action event
