I've done something similar in the past. Rather than rely on the restlet access logging service, I collected all the data I needed in an object as the request was processed. After the request completed, I spun off another thread to write to the log object to the database. If the database wasn't available, I did backup logging to a file. I _think_ I did this in the confines of wither log4j or slf4j, but I can't remember.
On Sun, Apr 3, 2011 at 8:31 PM, Paul Morris <pmor...@nmh.org> wrote: > I've been looking into this since my initial post and want to add a couple > of thoughts to clarify my intention here. I found the LogService Restlet > class which looks very robust but I need to customize some of the logging > here for auditing and compliance purposes (i.e. identify the user based on > querying a session server using a token) so I think I'm looking at something > homegrown. But again, I'd like to implement some way to sort of "copy" the > request on the way in and "copy" the response on the way out, parse through > those copies (perhaps in another thread) to break them out cleanly into a > database. > > ------------------------------------------------------ > > http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2716636 > ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2719277
