directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn McKinney (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FC-28) The safeText method is probably not useful, and can be faster
Date Sat, 07 Jul 2018 00:16:00 GMT

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

Shawn McKinney updated FC-28:
-----------------------------
    Fix Version/s:     (was: 2.0.1)

> The safeText method is probably not useful, and can be faster
> -------------------------------------------------------------
>
>                 Key: FC-28
>                 URL: https://issues.apache.org/jira/browse/FC-28
>             Project: FORTRESS
>          Issue Type: Improvement
>    Affects Versions: 1.0-RC35
>            Reporter: Emmanuel Lecharny
>            Priority: Major
>
> When we want to validate an entity before injecting it in the server, we call the RegExUtil.safeText()
method.
> It's checking something the server will already check (each value injected in the server
will be controlled). Of course, we can set limits like the max length, but this can be done
when defining the AttributeType (using the
> {NNN}
> notation).
> Otherwise, the way the regexp is evaluated is costly : we compile the gexep every time,
when it could be done only once.
> Pattern safeTextPattern = Pattern.compile(safeTextPatternStr);
> can be done globally.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message