Things that go IO in software

Sending something someplace in software involves a variety of io systems with differing specs on what constitutes th destination pointer. Files like "c:/soft" and stdio and FILE *, sockets have fd, they have "127.0.0.1" and PORT, And they all might have a protocol family: text or binary. The total necessary components to hold them all is the inner join of them with context definition for some variables.

So I have this container, it can have address, family type, fd, void * to something. It is set up to fit socket standards at the base, and build one or two items above that after padding. One single chunk of memory that has variable access for any type of destination. Its work to fill variable values, but the container holds space. I call it the generic Webaddr, but might change the name to IO_Thing. It's important because the machine always needs to flush things outward, and move itself back to empty.