4 ms·
The true evil approach is to send the socket around, not the message, so that there is no copying required no matter what ;)
by mononcqc 9y ago
The true evil approach is to send the socket around, not the message, so that there is no copying required no matter what ;)
- rdtsc 9y agoWah. Easy there, Satan :-) That is cool trick though. So it's basically sending the port itself around and changing its ownership, with something like port_connect(Port,NewOwner)? And btw, thank you for writing https://www.erlang-in-anger.com https://www.erlang-in-anger.com and http://learnyousomeerlang.com http://learnyousomeerlang.com !
- mononcqc 9y agoThe trick is more commonly used when writing to sockets. A socket owner is required for reading, not for writing. The trick then is that when you need to write lots of data to a socket to just send a copy of it to the writer so they can dump all their data for cheap, but without changing ownership (which is costly). Also recently I've gotten http://propertesting.com/ http://propertesting.com/ out, you might enjoy it :)
- rdtsc 9y agoThanks for explaining. I'll have to remember the socket trick. > Also recently I've gotten http://propertesting.com/ http://propertesting.com/ out, you might enjoy it :) It might be just what I need to understand and start using property tests. I've tried twice and gave up. Oh and recon! Thanks for that too. Use it almost every day.