New Feature: Request/Response log

[GoogleCodeExporter]

Sometimes when doing a testing / troubleshooting session, it can be very 
helpful to see multiple 
requests and their responses. It'd be *very* helpful if there was a Request Log 
window/pane/tab/drawer/whatever which allowed one to browse each request and 
response from 
the current session.

Once we have that, it'd also be great to have features to save the log, and 
clear the log.

Original issue reported on code.google.com by aviflax on 18 Feb 2008 at 7:55

• Merged into: New Feature: a way to view a Request/Response as a textual dialog #29

[GoogleCodeExporter]

Original comment by subwiz on 3 Mar 2008 at 1:52

• Added labels: 3.0

[GoogleCodeExporter]

Steps towards implementing this feature:

1. RequestBean -- implement toString() -- this information will be shown to the 
user
in the list of request/response.
2. The storage format needs to be defined. My preferred format is MimeMultipart
(http://java.sun.com/products/javamail/javadocs/javax/mail/internet/MimeMultipar
t.html).
 Each request-response will be stored separated by a boundary marker.
3. UI implementation.

Original comment by subwiz on 24 Mar 2008 at 11:44

• Changed state: Accepted

[GoogleCodeExporter]

subwiz, I think we just need to record the stream. We add a new log tab in 
request
and response, and display all the content. just like the attachment?

Original comment by libing.c...@gmail.com on 27 Mar 2008 at 12:33

Attachments:

• request_and_reponse_log.png

[GoogleCodeExporter]

I don't think this as a tab in request and response.

This has to be a separate window--which records each and every request made. 
This
window should be accessible from Tools>Session. This window will have a JTable
listing all the request/response made till now (from the time of opening Session
window). Each entry in the JTable would be toString() representation of 
RequestBean.
Clicking on any of the entry will load the corresponding request and response in
RESTClient window. 

Finally this sequence should be savable, so that it can be opened later for
execution. I think this would be more useful as we can see a series of 
executions one
by one.

This is what I have envisioned. And the only task I was able to finish till 
date was
the toString() portion :-)

Original comment by subwiz on 27 Mar 2008 at 12:49

[GoogleCodeExporter]

One of the options for saving the sequence would be to use the MIME format. We 
could use:

http://james.apache.org/mime4j/

Original comment by subwiz on 2 Apr 2008 at 1:14

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Me moved to my first employer after series of unsatisfying jobs. Now full of 
energy,
I have started developing this feature.

Original comment by subwiz on 2 Jul 2008 at 2:16

[GoogleCodeExporter]

http://hc.apache.org/httpcomponents-client/logging.html

We can write a log appender which captures all the logs and displays in a 
window.

Original comment by subwiz on 20 Mar 2009 at 1:16

[GoogleCodeExporter]

Original comment by subwiz on 7 Dec 2013 at 3:49

• Changed state: Duplicate