You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Jinmei Liao (JIRA)" <ji...@apache.org> on 2016/11/03 17:55:59 UTC

[jira] [Commented] (GEODE-2057) reorganize security packages

    [ https://issues.apache.org/jira/browse/GEODE-2057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15633642#comment-15633642 ] 

Jinmei Liao commented on GEODE-2057:
------------------------------------

 Rather than having a org.apache.geode.security.templates package [31] in the public API, I might consider moving these classes to the examples.  I would not want users thinking these Security classes/components are actually sufficient to securing Geode in a production environment (yikes)!

Additionally, I would probably even package the classes under org.apache.geode.security [32] a bit differently, having more organization/cleanliness with sub-packages.  The security packages feels like a dumping ground for anything and everything, all handling related but slightly different things, functionally... client vs. the server, authentication vs. authorization, securing communication channels, managing over all security, etc, etc.  Organization is the key to architecture and making things easy to consume and understand by users.

> reorganize security packages
> ----------------------------
>
>                 Key: GEODE-2057
>                 URL: https://issues.apache.org/jira/browse/GEODE-2057
>             Project: Geode
>          Issue Type: Sub-task
>            Reporter: Jinmei Liao
>
> move everything under org.apache.geode.internal.security into org.apache.geode.security.internal



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