Activity
From 12/10/2022 to 01/08/2023
12/21/2022
- 01:19 PM Feature #6939: improve proxy performance by hard-coding method invocation
- The correct patch is this, forgot to do @bzr add@ before doing @bzr diff@.
- 11:55 AM Feature #6939: improve proxy performance by hard-coding method invocation
- Greg Shah wrote:
> Yes, I was planning for all performance work to go in there.
OK, but not all performance work fr... - 09:42 AM Feature #6939: improve proxy performance by hard-coding method invocation
- Yes, I was planning for all performance work to go in there.
- 09:39 AM Feature #6939: improve proxy performance by hard-coding method invocation
- Greg Shah wrote:
> Do you have an updated version of the patch for 3821c? It does not apply cleanly on 3821c rev 14... - 09:36 AM Feature #6939: improve proxy performance by hard-coding method invocation
- Do you have an updated version of the patch for 3821c? It does not apply cleanly on 3821c rev 14461.
Eric: This s... - 03:55 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...
- I'm not working on this task at the moment, but I randomly got an idea and just want to document it here, since we mi...
12/19/2022
- 05:09 PM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration
- > > Right now, I don't foresee any changes to conversion needed. If that changes, I would agree with this idea.
>
... - 06:51 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration
- Greg Shah wrote:
> Galya Bogdanova wrote:
>
> > *Conversion* code should be reworked to not be broken by upcoming ...
12/16/2022
- 09:50 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration
- Greg Shah wrote:
> We need both server side and client side logging. I think most of the time the server side appro... - 09:33 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration
- > > We are at a point where we are still heavily modifying our implementation and that includes our external API.
> ... - 09:33 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration
- Yes, @LogHelper@ can be changed.
- 09:32 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration
- Greg Shah wrote:
> We are at a point where we are still heavily modifying our implementation and that includes our e... - 09:31 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration
- Greg Shah wrote:
> At this time, I don't see how our 4GL-compatibility needs to change for this task, but I may be m... - 09:29 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration
- > If some FWD users want to develop their new Java code extending their app functionality, do they import / integrate...
- 09:25 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration
- > * Each system process should have a separate log file.
Yes
> * Screen / client drivers output on the screen e... - 06:49 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration
- A question: If some FWD users want to develop their new Java code extending their app functionality, do they import /...
- 07:24 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...
- Please focus on #5703 first and pause work on this task.
- 05:48 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...
- Galya Bogdanova wrote:
> The Windows spawner creates the new process with all the needed attributes as it is now, bu... - 03:01 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...
- Galya Bogdanova wrote:
> That's where we set a @stdout@ handler to the properly renamed filename and execute the @cm... - 02:52 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...
- I have another idea of how to solve the pid issue on Windows.
The Windows spawner creates the new process with all... - 02:30 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...
- Greg Shah wrote:
> I think you can try any 4GL code which uses @DISPLAY@, @PUT@ or similar output statement without ...
12/15/2022
- 02:56 PM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...
- > I need an ABL procedure that outputs to outputToFile to test it out.
I think you can try any 4GL code which uses... - 01:17 PM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...
- I'm attaching a diff for a demo implementation of how @%pid%@ replace and @stdout@ redirect can work in Java for back...
- 09:00 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...
- > Run the cmd in the spawner process itself. This looks like a more dangerous exercise, since I don't fully understan...
- 07:26 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...
- My proposal cannot actually work for Windows where @CreateProcess@ creates an independent new process without any ref...
- 11:02 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration
- I'll use this comment to summarize the types of log files we ultimately need (it'll be updated additionally).
---... - 09:01 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration
- A related issue to be addressed by the change, as described in #4331:
> Standalone clients (confirmed for gui_swin...
12/12/2022
- 04:34 PM Bug #5699 (Closed): broken logfile name on Windows appserver clients (and probably other cases on...
- 01:28 PM Bug #5699: broken logfile name on Windows appserver clients (and probably other cases on Windows)
- I ran the server on Windows with a batch process and was able to confirm the new behavior of the spawner of properly ...
- 01:29 PM Feature #6939: improve proxy performance by hard-coding method invocation
- Some additional notes:
* having both consumer and function lambdas doesn't really have a functional benefit, only fu... - 10:32 AM Feature #6939: improve proxy performance by hard-coding method invocation
- Eric, please review attached patch - it adds a invocation handler like this:...
Also available in: Atom