History log of /system/bt/osi/include/socket.h
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
d2199cbb8f361772819402b56e6fa46587a31c56 18-Aug-2015 Pavlin Radoslavov <pavlin@google.com> Disable remote TCP connections

For security reasons, TCP sockets now listen on the loopback
IPv4 address 127.0.0.1 for incoming TCP connections.

Bug: 23272146
Change-Id: I88523f643f305f2281740575d7011b6077bf0843
/system/bt/osi/include/socket.h
98bf85fea392258ba22a252eeeed1153dc3eb16f 28-Aug-2014 Sharvil Nanavati <sharvil@google.com> Add a method to check for available bytes on a socket

The available bytes function shouldn't normally be required (and
if it is, the code design is probably bad and should be rethought) but
is introduced as a stop-gap until we can redesign the BTA code that
expects a priori knowledge of the number of bytes that can be read from
the socket.

This change also relaxes the requirement that on socket_register that
at least one of read_cb or write_cb must be specified.
/system/bt/osi/include/socket.h
ad3067b83e4d309b4027a4e9b44b0a614f267da8 22-Aug-2014 Sharvil Nanavati <sharvil@google.com> Add a method to pass file descriptors and one to create a socket from an fd.
/system/bt/osi/include/socket.h
fbf89085bf308a98b00da77d1538539f6dd58604 13-Aug-2014 Sharvil Nanavati <sharvil@google.com> Switch to an epoll-based reactor implementation.

epoll is a much nicer interface that very closely matches the
reactor interface. It's also thread-safe which makes it a more
suitable choice for bluedroid. As a result of this change,
reactor_register and reactor_unregister are both thread-safe without
introducing any synchronization in user-space.
/system/bt/osi/include/socket.h
ed7095be083ffe47f8b9d0d3090b0f2e109b8125 05-Aug-2014 Zach Johnson <zachoverflow@google.com> Fix socket to use safe reactor registration
/system/bt/osi/include/socket.h
c2031c4fbab9ed2d2e51a0b287a3fab805932ca4 26-Jul-2014 Sharvil Nanavati <sharvil@google.com> Introduce a socket class

This socket implementation is limited to TCP server sockets and
provides no mechanism to connect to a remote host. It's primarily
intended to be used to interface with debugging tools. It's designed
to work seamlessly with the reactor (event-driven) model.
/system/bt/osi/include/socket.h