Hi,
I think we've found a bug in crary. We cannot pass any option as
socket_opts in crary:start/4, crary_port either dismisses it or crashes.
The problem is in crary_port:sock_opts/1, attached patch solves it (but
changes the policy from conservative to permissive, so better make sure
it's ok before applying it to next version).
Best regards
--
Samuel Rivas
R&D and Base Development Leader
t:+34 981 17 33 44 f:+34 981 29 66 55
www.lambdastream.com
--
Samuel
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"erlware-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/erlware-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
Index: src/crary_port.erl
===================================================================
--- src/crary_port.erl (revision 914)
+++ src/crary_port.erl (working copy)
@@ -198,6 +198,7 @@
({exit_on_close, _}) -> false;
({header, _}) -> false;
({packet, _}) -> false;
- ({packet_size, _}) -> false
+ ({packet_size, _}) -> false;
+ (_) -> true
end,
proplists:get_value(socket_opts, Opts, [])).
