Hi all, I'm looking into adding socket streaming support to iv. Before I begin I would love any advice on how to approach this task. I've read through the socket.imageio code and I see that SocketInput is a server and SocketOutput is a client. Despite the fact that SocketInput/Output are implemented as ImageInput/Output subclasses, they are somewhat non-standard -- for starters, there is no file on disk and the file "name" is actually the host/port -- so it seems that socket "images" will likely need special treatment within iv. For example, we'll probably want a menu item to start the server to listen for incoming renders.
I'm wondering how compatible the socket.imageio format is with the other formats displayed by iv. Typically the entirety of an image is expected to exist prior to loading, so iv can call read_native_scanline/read_native_tile at its discretion to read in the image. however, in the case of SocketOutput/Input I assume that we will have to convey to iv that tiles are ready as they are produced, or is that already handled by the ImageInput/Output API already? thanks! -chad _______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
