You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ratis.apache.org by "Enis Soztutar (JIRA)" <ji...@apache.org> on 2017/03/29 18:31:41 UTC

[jira] [Created] (RATIS-52) Refactor RaftUtils into different classes

Enis Soztutar created RATIS-52:
----------------------------------

             Summary: Refactor RaftUtils into different classes
                 Key: RATIS-52
                 URL: https://issues.apache.org/jira/browse/RATIS-52
             Project: Ratis
          Issue Type: Improvement
            Reporter: Enis Soztutar


Ideally we should not have a generic {{RaftUtils}} class. The code should be broken up into at least: 
{code}
ReflectionUtils -> All reflection, construction, initialization logic 
IOUtils -> Add buffer and IO logic 
SystemUtils or PlatformUtils -> OS type detection, etc 
Preconditions (or something like that) -> assertTrue, etc 
{code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)