You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Ayoma Wijethunga (JIRA)" <ji...@apache.org> on 2015/06/10 08:21:02 UTC

[jira] [Updated] (VALIDATOR-341) Make TLD list configurable

     [ https://issues.apache.org/jira/browse/VALIDATOR-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ayoma Wijethunga updated VALIDATOR-341:
---------------------------------------
    Attachment: RequestForComments.patch

As a validation utility, my idea is that we should provide a simple mechanism of extending the TLD list. If such custom configuration is required for a particular user, the user should be allowed to decide how custom configurations should be stored and managed (serialization / flat files). 

I have attached a patch with this comment and I welcome any comments and suggestions regarding how to further improve the patch. If the patch is up to expectation and is pointing towards the correction direction, I can write additional unit tests and provide a full patch.

However, if team suggests that we should allow user to extend the lists based on a file input, it is always possible to provide additional wrapper methods that accept File object or so on.

> Make TLD list configurable
> --------------------------
>
>                 Key: VALIDATOR-341
>                 URL: https://issues.apache.org/jira/browse/VALIDATOR-341
>             Project: Commons Validator
>          Issue Type: New Feature
>          Components: Framework
>            Reporter: Benedikt Ritter
>              Labels: TLD, domains, email
>         Attachments: RequestForComments.patch
>
>
> Since the list of valid TLDs changes from time to time, it makes sense to let users configure the list of valid TLDs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)