Ticket #4 (assigned enhancement)
Allow saving and restoring the browser state.
|Reported by:||bringert||Owned by:||sof|
---------- Forwarded message ---------- From: Will Thompson <email@example.com> Date: Thu, May 22, 2008 at 8:00 PM Subject: Patches for HTTP.Browser to allow saving and restoring the state. To: firstname.lastname@example.org 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 TracTickets for help on using tickets.