[
https://issues.apache.org/jira/browse/MESOS-7452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Peach updated MESOS-7452:
---
Description: libprocess throws away the peer address from {{accept(2)}} and
doesn't cache the results from {{getpeername(2)}}, but it would be convenient
to be able to call {{Socket::peer}} without making a system call each time. We
should investigate what it takes to cache the peer address in the {{Socket}}
object. (was: libprocess throws away the peer address from `accept(2)` and
doesn't cache the results from `getpeername(2)`, but it would be convenient to
be able to call `Socket::peer` without making a system call each time. We
should investigate what it takes to cache the peer address in the `Socket`
object.)
> Cache the peer address on the libprocess Socket.
>
>
> Key: MESOS-7452
> URL: https://issues.apache.org/jira/browse/MESOS-7452
> Project: Mesos
> Issue Type: Bug
> Components: libprocess
>Reporter: James Peach
>Priority: Minor
>
> libprocess throws away the peer address from {{accept(2)}} and doesn't cache
> the results from {{getpeername(2)}}, but it would be convenient to be able to
> call {{Socket::peer}} without making a system call each time. We should
> investigate what it takes to cache the peer address in the {{Socket}} object.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
