Daniel L. Rall wrote:
Jochen, I defer to John on the timezone interpretation of what's generally accepted as output by common server implementations. However, like usual, I'm of the opinion that servers should be gracious about the types of input accepted, so long as doing so isn't explicitly against the specs (XML-RPC and ISO 8601 apply here), or overly complicates the code. Assuming your patches to parse time zone and to interpret millis follow these rules, send'em over. However, for the sake of interoperability with less forgiving servers, our client will not generate output of this less-common sort.
I'll query [EMAIL PROTECTED], whether the DateFormat classes can be moved to some common jar file.
Interesting -- what package does that date formatting code belong to now? If it's homeless, I wouldn't mind adding it to Jakarta Commons Lang. Use of a third-party JAR is reasonable for HEAD (2.0), which has more dependencies, but not ideal for 1.2 (or any 1.x release), which does not include much in the way of external dependencies.
If so, I'll post a patch using the DateFormat from the jar file for reading. Otherwise, I'll post a patch using a copy of XsDateFormat. Ok?
Excuse my ignorance, but what is XsDateFormat and from whither does it hale?
- Dan
