-
Notifications
You must be signed in to change notification settings - Fork 10
[Network] allow setting socket options #106
Comments
Unless I'm missing something, the HHVM issue is not relevant here - the sockets are created with |
HHVM doesn't support no-dely / keep-alive 😞 |
That doesn't appear to be the case
|
that said, retitled as I won't be doing these in small batches; there's many SO_ and TCP_ options, and I'm hoping to avoid adding something as rough as |
😱 i clearly remember they didn't exist back when i was working on #36
wouldn't using a shape be "stricter" ? e.g, |
perhaps - probably separate shapes, then TCP\Conenct would take shape('socket_options' => SocketOptionsShape', 'tcp_options' => TcpOptionsShape) or something like that or options -> socket, options -> tcp |
or maybe tcp options shape can have all socket options therefore it can be passed as both ? :) |
When we move to native implementaitons, I'm probably going to change all timeouts to be ints, or something like the
|
Looks like they were added in 2015; for both #36 and the HHVM issue, you were specific about the |
probably 🤔 |
Splat would be really nice here; there's a few (SO_NREAD, SO_ERROR, SO_NWRITE in particular) that it would be nice to type as invalid for setsockopt, but valid for getsockopt, without duplciating the entire shape |
see: facebook/hhvm#8451The text was updated successfully, but these errors were encountered: