{5} Assigned, Active Tickets by Owner (Full Description) (2 matches)
List tickets assigned, group by ticket owner. This report demonstrates the use of full-row display.
sof (2 matches)
| Ticket | Summary | Component | Milestone | Type | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #3 | Expose HTTP header parsing | component1 | enhancement | 09/10/08 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---------- Forwarded message ---------- From: Tim Newsham <newsham@lava.net> Date: Wed, Sep 3, 2008 at 11:03 PM Subject: Network.HTTP To: bjorn@bringert.net I'm looking for a library that can parse HTTP messages. I noticed that Network.HTTP, which you maintain, generates and parses HTTP messages but only the generator is exposed externally (through the Show interface). Would it be possible to make a version which exposes parsing as well? For example, through a Read interface... Tim Newsham http://www.thenewsh.com/~newsham/ |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #4 | Allow saving and restoring the browser state. | component1 | enhancement | 09/10/08 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---------- Forwarded message ---------- From: Will Thompson <will@willthompson.co.uk> Date: Thu, May 22, 2008 at 8:00 PM Subject: Patches for HTTP.Browser to allow saving and restoring the state. To: bjorn@bringert.net Hi, My application needs to go through a bunch of authentication steps before it can make any useful requests. Currently, I can either do all the steps every time, or rebuild the browser state manually by saving getCookies and getAuthorities; the attached patches add a function browseS that allows the initial state of the browser to be given by the user, and returns the final state along with the BrowserAction's result. (This also includes the previous patch I sent, removing an 'error' call from defaultBrowserState, as it is a dependency of the new patches.) Is sending you patches directly the right thing to be doing? Thanks, -- Will |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Note:
See TracReports for help on using and creating reports.
