You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4php-dev@logging.apache.org by "Ivan Habunek (Created) (JIRA)" <ji...@apache.org> on 2011/10/02 20:16:34 UTC
[jira] [Created] (LOG4PHP-154) Rewrite LoggerAppenderSocket to use
a layout
Rewrite LoggerAppenderSocket to use a layout
--------------------------------------------
Key: LOG4PHP-154
URL: https://issues.apache.org/jira/browse/LOG4PHP-154
Project: Log4php
Issue Type: Improvement
Components: Code
Affects Versions: 2.1
Reporter: Ivan Habunek
Currently, the socket appender does not require a layout. The layout is internally configured by using the "useXml" option. If useXml is set to true, events are formatted as XML, and if set to false, they are serialized.
A better solution would be to make LoggerAppenderSocket use a layout so the user can pick which layout to use the standard way.
To keep all functionality, a new layout should be coded which outputs serialized event objects. This should be made default layout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (LOG4PHP-154) Rewrite LoggerAppenderSocket to use
a layout
Posted by "Ivan Habunek (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LOG4PHP-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan Habunek reassigned LOG4PHP-154:
------------------------------------
Assignee: Ivan Habunek
> Rewrite LoggerAppenderSocket to use a layout
> --------------------------------------------
>
> Key: LOG4PHP-154
> URL: https://issues.apache.org/jira/browse/LOG4PHP-154
> Project: Log4php
> Issue Type: Improvement
> Components: Code
> Affects Versions: 2.1
> Reporter: Ivan Habunek
> Assignee: Ivan Habunek
> Labels: appender, layout, socket
>
> Currently, the socket appender does not require a layout. The layout is internally configured by using the "useXml" option. If useXml is set to true, events are formatted as XML, and if set to false, they are serialized.
> A better solution would be to make LoggerAppenderSocket use a layout so the user can pick which layout to use the standard way.
> To keep all functionality, a new layout should be coded which outputs serialized event objects. This should be made default layout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (LOG4PHP-154) Rewrite LoggerAppenderSocket to use
a layout
Posted by "Ivan Habunek (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LOG4PHP-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan Habunek resolved LOG4PHP-154.
----------------------------------
Resolution: Fixed
Fix Version/s: 2.2
> Rewrite LoggerAppenderSocket to use a layout
> --------------------------------------------
>
> Key: LOG4PHP-154
> URL: https://issues.apache.org/jira/browse/LOG4PHP-154
> Project: Log4php
> Issue Type: Improvement
> Components: Code
> Affects Versions: 2.1
> Reporter: Ivan Habunek
> Assignee: Ivan Habunek
> Labels: appender, layout, socket
> Fix For: 2.2
>
>
> Currently, the socket appender does not require a layout. The layout is internally configured by using the "useXml" option. If useXml is set to true, events are formatted as XML, and if set to false, they are serialized.
> A better solution would be to make LoggerAppenderSocket use a layout so the user can pick which layout to use the standard way.
> To keep all functionality, a new layout should be coded which outputs serialized event objects. This should be made default layout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira