[jira] [Resolved] (ARTEMIS-1907) Confusion between AIO and ASYNCIO

["Justin Bertram (JIRA)" <ji...@apache.org>]

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

Justin Bertram resolved ARTEMIS-1907.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.6.1

> Confusion between AIO and ASYNCIO
> ---------------------------------
>
>                 Key: ARTEMIS-1907
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1907
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>            Reporter: Lionel Cons
>            Priority: Minor
>             Fix For: 2.6.1
>
>
> It seems that, in the user manual at least, there is a confusion between {{AIO}} and {{ASYNCIO}}.
> For instance, https://activemq.apache.org/artemis/docs/latest/persistence.html contains:
> {quote}
> The second implementation uses a thin native code wrapper to talk to the Linux asynchronous IO library (AIO). With AIO, Apache ActiveMQ Artemis will [...]
> {quote}
> and further down:
> {quote}
> journal-type: Valid values are NIO, ASYNCIO or MAPPED
> {quote}
> In https://activemq.apache.org/artemis/docs/latest/using-server.html we even have:
> {quote}
> --aio Sets the journal as asyncio.
> {quote}
> Looking at numbers, it seems that {{AIO}} is used more than {{ASYNCIO}}:
> {code}
> $ grep -wri aio docs/user-manual | wc -l
> 29
> $ grep -wri asyncio docs/user-manual | wc -l
> 5
> {code}
> Using only one term everywhere would be more consistent and clearer for the reader.



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