> - The worker creates it’s own log file - thus no contention issues.
Exactly. That's how servers write log files. File contention at the OS
level is an drenched pit filled with leeches. It's also "slow". Actually,
slow is an issue with logs - if you'r streaming a lot of entries.
So, yes, it's def
David:
Log files - love them too. Saved huge amounts of time to debug code (at least
all the bugs I create ;-) )
In our shell I am trying to stay away from plugins - what we and others do with
the shell for specific projects after that does not matter.
What I have done for logs thus far in the
On Wed, Jul 26, 2017 at 9:04 AM, Jeffrey Kain via 4D_Tech <
4d_tech@lists.4d.com> wrote:
> Thanks for the heads up. This was going to be the #1 project after
> upgrading to v16... creating workers to handle logging.
>
Yeah, CALL WORKER is the *perfect* design for this, unless you can't afford
to
Thanks for the heads up. This was going to be the #1 project after upgrading to
v16... creating workers to handle logging.
--
Jeffrey Kain
jeffrey.k...@gmail.com
> On Jul 25, 2017, at 7:01 PM, David Adams via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
> It took me about 15 minutes to stumble ac
Jeff,
Probably unrelated, but I've had a bug on file for months (V16 and later,
if I remember correctly) having to do with the file system and CALL WORKER.
Weird race conditions that lead to a crash (Windows) or something like 21
identically named "unique" worker processes and then you're stuck (a
There was no code at all in the debug log prior to the reception of the outside
call event.
--
Jeffrey Kain
jeffrey.k...@gmail.com
> On Jul 25, 2017, at 6:55 PM, Chuck Miller via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
> If there are object scripts they run before form method
*
If there are object scripts they run before form method
Regards
Chuck
Sent from my iPhone
> On Jul 25, 2017, at 6:51 PM, Jeffrey Kain via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
> 've verified the "no code runs" part both by setting a break point in the
> first line of the form method of
Has anyone else seen some really strange bugs with the Open Document command on
Sierra?
One manifestation:
Process 1:
Display a form
From the form, open a dialog box ("d1")
Call open document
Close the document
Close the dialog ("d1")
(Now you're back at the form)
Process 2:
Do a
8 matches
Mail list logo
