[erlang-questions] inet_drv.c and packet type extensibility

[Paul Fisher]

Currently it appears that adding new packet types, in the way HTTP is
supported, involves adding code directly to
tcp_reply_data()/tcp_reply_binary_data().  Is there any plan/desire to
have a level of extensibility in order to facilitate additional packet
driver implementations?  (BTW, my interest is in adding BEEP support.)

Or maybe at this point there is very little to gain in having this level
of protocol handling in the driver, and new such implementations are
just as well served implemented directly in erlang?  Guidance would be
appreciated.


--

paul