Version 5.0...

Hey guys.

I was thinking recently about sites that are really heavy on cookies, and it proves cumbersome to dance around with scripts to set the values. It's sometimes hard to keep my eye on everything when cookies aren't viewable from a tab on a ScrapeableFile, like the Parameters are enumerated.

Is it possible to get a revised cookie interface in 5.0? I really start to see a tab as a via interface as I've watched the Compare Proxy Transaction tool develop into having such a tab.

I realize this would probably require a different internal code approach to running scrapeable files, but I think its usability proves immensely more flexible than relying on extensive usage of before- and after-ScrapeableFile calls for the sake of session.setCookie(). Additionally, a tab dedicated to cookies would let screen-scraper automatically understand the implied base domain for the cookie's domain scope, instead of needing to hard code it into each cookie. For true flexibility, perhaps it could simply allow the "domain" part of the cookie definition to be blank by default, to imply "whatever the base domain calculates to" (given variables in the URL field). Then if the user needs to set a cookie for some other domain text (like subdomains, etc), they can change the blank "domain" field to explicit text.

Just an idea.

Tim