Thanks Michael - that looks encouraging and I shall try it. First though, I'm a little concerned that the software may not be able to do what I want, as I've tried several approaches using the one-man code fork previously described, without any success. What I want to do is to be able to get onto this page:
http://www.racingpost.co.uk/horses/?MIval=v2_a_days_racing&day=04&month=Jan&; year=2004&flag=3 which is (subject to parameter changes) a link in the menu called 'Future racing' at that page. Do you think this IS possible, and if so, how should it be done? Charles Johnson ----- Original Message ----- From: "Michael Becke" <[EMAIL PROTECTED]> To: "Commons HttpClient Project" <[EMAIL PROTECTED]> Sent: Friday, January 02, 2004 10:07 PM Subject: Re: DateParser pluggability > Hello, > > Date parser formats can be configured in the post 2.0 HttpClient code. > This code, in CVS HEAD, is still pre-alpha but everything should still > be working. You can add a format using something like the following: > > HttpParams params = DefaultHttpParams.getDefaultParams(); > HashSet patterns = new HashSet((Collection) > params.getParameter(DateParser.KEY_DATE_PATTERNS)); > patterns.add("SOME_PATTERN"); > params.setParameter(DateParser.KEY_DATE_PATTERNS, patterns); > > Mike > > On Dec 31, 2003, at 10:57 AM, protean wrote: > > > I have had to supply an extra format String as follows: > > > > /** The patterns used for parsing dates */ > > private static final String[] DATE_PATTERNS = { > > PATTERN_RFC1123, > > PATTERN_RFC1036, > > PATTERN_ASCTIME, > > "EEE, dd-MMM-yyyy HH:mm:ss z", > > "EEE, dd-MMM-yyyy HH-mm-ss z", > > "EEE, dd MMM yy HH:mm:ss z", > > "EEE dd-MMM-yyyy HH:mm:ss z", > > "EEE dd MMM yyyy HH:mm:ss z", > > "EEE dd-MMM-yyyy HH-mm-ss z", > > "EEE dd-MMM-yy HH:mm:ss z", > > "EEE dd MMM yy HH:mm:ss z", > > "EEE,dd-MMM-yy HH:mm:ss z", > > "EEE,dd-MMM-yyyy HH:mm:ss z", > > "EEE, dd-MM-yyyy HH:mm:ss z", > > // Extra for non-compliant site > > "dd-MMM-yyyy HH:mm:ss zzz" > > }; > > > > to the DateParser class and produce my own build, as the DateParser > > does not > > seem to provide pluggability for non-compliant sites. Can anyone tell > > me when > > this situation may change so I no longer have to produce a one-man > > code fork? > > > > C Johnson > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > > [EMAIL PROTECTED] > > For additional commands, e-mail: > > [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
