You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by bu...@apache.org on 2005/05/20 02:58:45 UTC

DO NOT REPLY [Bug 34978] - ftp systemTypeKey ought to have an "unknown" or "automatic" value

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=34978>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=34978





------- Additional Comments From scohen@apache.org  2005-05-20 02:58 -------
I think we can accomodate this but I'd like to get a little more familiar with
your use case.  There is a relationship between systemTypeKey and the other new
attributes:

If any of these new attributes (serverTimeZoneConfig, defaultDateFormatConfig,
recentDateFormatConfig, serverLanguageCodeConfig, shortMonthNamesConfig) is
specified and systemTypeKey isn't, a default system type of UNIX is selected. 
If none is selected and the systemTypeKey ISN'T chosen, then the old default
autodetect mechanism is used.

The reason for this is that the five new attributes must be applied to a parser
object which must precreated to be of some particular system type.  In the
autodetect scheme, it is assumed that the "normal" configuration for the
autodetected system type will be used and this type will be determined by that.

In other words, there are two use cases here.  One for specifying a connection
to a specific server with non-standard characteristics (non-English month names,
all-numeric timestamp listings in a server type where this is not the norm, a
time zone different from that of the client).  The other says, autodetect and
I'll take my chances, this system is vanilla.  That's the easier way and good
for most cases.  The other system is for the hard cases.

Now, in your property-driven use case, the question I want to ask is this:  Do
you want to specify some of these non-standard attributes sometimes and other
times not?  Or do you imagine you'll never need them?  If it's the latter, you
can just leave out systemTypeKey and just autodetect everything.

However, I suspect that that won't really suit.  So the right fix is to make all
the new attributes respect the convention that attribute="" is equivalent to not
specifying attribute at all.  Does that sound like it would work for what you
are trying to do?

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org