+1 for implementing this at transport level. Should go into ServerHandler#connected event IMO. When you implement this as a mediator, the user has to be aware of that and he has to explicitly put it into every sequence/service thus leading to an additional configuration overhead. This is the same reason why we should not be using mediators for collecting stats.
However other attributes such as the log file name and rolling behavior has to be configured through the log4j.properties file. We can name the log file access.log by default. We can also use the daily rolling file appender by default and allow the user to configure it according to his requirements and load. Thanks, Hiranya On Sun, Mar 13, 2011 at 8:19 AM, Afkham Azeez <[email protected]> wrote: > > > On Sun, Mar 13, 2011 at 8:15 AM, Sanjiva Weerawarana <[email protected]>wrote: > >> On Sun, Mar 13, 2011 at 8:04 AM, Afkham Azeez <[email protected]> wrote: >> >>> >>> Something similar. It is called http_access_2011-03-13.log, with the date >>> appended, and the file is rolled on daily basis. >>> >> >> Can we call it access.log as that's the usual name? Also appending the >> date is unnecessary and may not be enough rolling ... a highly accessed >> server may have that file grow very very big within a day. We should use the >> same rolling scheme as other logs. >> > > We can call it access.log, no problem there. But should we get rid of the > rolling? After a few weeks or months, that file can be extremely large, and > will increase the possibility of file corruption (due to possible bugs). So > it is safer to roll it on a daily basis. With our log4j log files, we do > daily rolling. We are using the DailyRollingFileAppender. > > >> >> Sanjiva. >> -- >> Sanjiva Weerawarana, Ph.D. >> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ >> email: [email protected]; phone: >> <%2B94%2011%20763%209614><%2B94%2011%20763%209614>+94 >> 11 763 9614; cell: <%2B94%2077%20787%206880> <%2B94%2077%20787%206880>+94 >> 77 787 6880 | <%2B1%20650%20265%208311> <%2B1%20650%20265%208311>+1 650 >> 265 8311 >> blog: http://sanjiva.weerawarana.org/ >> >> Lean . Enterprise . Middleware >> > > > > -- > *Afkham Azeez* > Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, > * > * > *Member; Apache Software Foundation; > **http://www.apache.org/*<http://www.apache.org/> > * > email: **[email protected]* <[email protected]>* cell: <%2B94%2077%203320919>+94 > 77 3320919 > blog: **http://blog.afkham.org* <http://blog.afkham.org>* > twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> > * > linked-in: **http://lk.linkedin.com/in/afkhamazeez* > * > * > *Lean . Enterprise . Middleware* > > > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Hiranya Jayathilaka Senior Software Engineer; WSO2 Inc.; http://wso2.org E-mail: [email protected]; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
