Hi Aaron, You are facing an interesting problem... The easiest way would be to pass this profiling information right inside your request and response entities.
Another way would be to log information into a shared storage (file, db, etc.) using unique request IDs to reconcile data. For this purpose, you might be interested by the ConnectorService#beforeSend() and afterSend() methods. Also, we don't support trailing HTTP headers and there is no plan yet to support them in the future. Best regards, Jerome -----Message d'origine----- De : news [mailto:[EMAIL PROTECTED] De la part de Aaron Crow Envoyé : samedi 2 août 2008 06:13 À : [email protected] Objet : Multi-tiered reporting of profiling information using custom headers? Hi Restlet Community, I'm working with a 3-tiered system, the bottom 2 tiers using Restlet. The higher Riestlet tier makes multiple requests down to the lowest Restlet tier, in order to serve a single one of its own requests. I'd like to start compiling meaningful profiling information per request. So I'd like each tier to pass info up to the next tier, to be collated and ultimately reported to the end user. (Assuming the end user is an inquiring developer who'd like to know a lot about "what just happened".) Do any of you have experience doing this kind of thing, and if so, any pointers for me? I've been warned to be careful about buffering of responses, since that can prevent me from having the oppopurtinity to add info via a custom header right at the tail end of a response. I'm not sure about this... is this a limitation with the Restlet framework? Are there any other limitations to be aware of as far as using custom headers for this purpose? Or any better approaches? Any thoughts or advice greatly appreciated... Best wishes, Aaron
