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

Posted to issues@mesos.apache.org by "Isabel Jimenez (JIRA)" <ji...@apache.org> on 2016/02/02 21:47:39 UTC

[jira] [Assigned] (MESOS-2814) os::read should have one implementation

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

Isabel Jimenez reassigned MESOS-2814:
-------------------------------------

    Assignee: Isabel Jimenez

> os::read should have one implementation
> ---------------------------------------
>
>                 Key: MESOS-2814
>                 URL: https://issues.apache.org/jira/browse/MESOS-2814
>             Project: Mesos
>          Issue Type: Improvement
>          Components: stout
>            Reporter: Cody Maloney
>            Assignee: Isabel Jimenez
>              Labels: mesosphere, tech-debt
>
> Currently stout os::read() has two radically different implementations when you give it a {{std::string}} vs. a {{const char *}}. Ideally these have one implementation that does things like intelligently size the buffer that it writes into rather than re-allocating repeatedly with every time it lengthens the string (resulting in copious copying). 



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