[ 
https://issues.apache.org/jira/browse/LOG4J2-3023?focusedWorklogId=915788&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-915788
 ]

ASF GitHub Bot logged work on LOG4J2-3023:
------------------------------------------

                Author: ASF GitHub Bot
            Created on: 22/Apr/24 11:22
            Start Date: 22/Apr/24 11:22
    Worklog Time Spent: 10m 
      Work Description: ppkarwasz commented on issue #2496:
URL: 
https://github.com/apache/logging-log4j2/issues/2496#issuecomment-2069142947

   I think we should introduce an `OutputStream` abstraction:
   
   ```java
   public interface OutputStreamWrapper {
   
       OutputStream wrap(OutputStream stream);
   }
   ```
   
   Such an abstraction could solve several issues:
   
   * it would allow users to introduce their own compression/decompression 
algorithms (apache/logging-log4j2#1508),
   * it would allow us to remove the dependency on `commons-compress` from 
Log4j Core,
   * it would allow users to implement some sort of end-to-end encryption (cf. 
[LOG4J2-1000](https://issues.apache.org/jira/browse/LOG4J2-1000) and 
[LOG4J2-2930](https://issues.apache.org/jira/browse/LOG4J2-2930)).




Issue Time Tracking
-------------------

    Worklog Id:     (was: 915788)
    Time Spent: 20m  (was: 10m)

> Create a wrapper layout compressing the output of the delegate
> --------------------------------------------------------------
>
>                 Key: LOG4J2-3023
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-3023
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Volkan Yazici
>            Assignee: Volkan Yazici
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> There are cases where the output of a layout needs to be compressed, e.g., 
> {{GelfLayout}}. Rather than implementing this functionality individually for 
> each layout, this story aims to create a wrapper to perform this operation.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to