Date | Commit message (Collapse) |
|
Of course these fields are not portable between Linux and FreeBSD,
but they should remain ABI-compatible for future versions of each OS.
Tested on FreeBSD 10.3-RELEASE i386
TCP state names will be another problem...
|
|
This provides some extra type safety if combined with other
C extensions, as well as allowing us to account for memory usage of
the HTTP parser in ObjectSpace.
This requires Ruby 1.9.3+ and has remained a stable API since
then. This will become officially supported when Ruby 2.3.0 is
released later this month.
This API has only been documented in doc/extension.rdoc (formerly
README.EXT) in the Ruby source tree since April 2015, r50318
|
|
While #get! is the same as the #initialize method,
the former is public and called explicitly by folks
wishing to reduce allocation overhead.
|
|
Defining the "Raindrops" class explicitly helps RDoc find
subclasses for documentation, and ought to reduce the binary
size slightly due to the removal of rb_intern calls.
Furthermore, use "Socket" to ensure the base class for
Raindrops::InetDiagSocket is documented properly in RDoc.
|
|
While raindrops.bogomips.org exists, having extra subjectAltName
entries is bloating the certificate. This will make it easier
to mirror the homepage on Tor hidden services.
|
|
The linux/tcp.h header may not exist on alternative libc
implementations such as musl.
Noticed-by: Doug Forster <doug.forster@gmail.com>
|
|
This allows reusing existing Linux::TCP_Info objects to avoid
generating garbage.
|
|
We can't even pull in linux/*.h headers to check
for TCP_INFO.
|
|
It's useful, yes.
|
|
Of course, RDoc doesn't know quantity vs quality :)
|
|
It's more complete for people on ancient systems where
"struct tcp_info" is defined in netinet/tcp and missing
tcp_ircv_rtt, tcpi_rcv_space and tcpi_total_retrans.
|
|
This returns a Raindrops::TCP_Info object
that wraps a tcp_info struct.
|