On Jun 21, 2012, at 7:11 PM, Chad Dombrova wrote:
> cool. then all this is done. I've written a SocketServer class that listens
> for incoming connections and calls a callback with the incoming file name. I
> currently have it as part of openImageIO library. Does that work for you?
Yes. This aspect of socket input is a very special case that falls outside the
bounds of the nice API we have for everything else. I don't mind adding a
separate function just for that.
> the next thing i need to do is figure out edge tiles, as we discussed a bit
> earlier. the SocketInput receives "cropped" tiles over the socket, but the
> pointer passed in from the ImageCache is handing it "full" tiles. I saw some
> recent commits related to this discussion: is it still the case that the
> ImageCache allocates "full" memory for "cropped" tiles?
Yes, that did not change. ImageCache will allocate a "full" tile even for
partially-filled edge tiles. But that shouldn't matter to you; you don't need
to modify ImageCache at all. When somebody calls ImageInput::read_tile(), they
pass the strides and read_tile does not alter "nonexistant" pixels, so the
caller has the choice of whether they want the read_tile to fill in a
"full-sized tile" or a "just-right partial tile".
There were some recent changes (which are now committed to both the trunk and
RB-1.0) that fixed some of that stride handling of the partial tiles. I think
you definitely want those changes if you don't already have them.
-- lg
--
Larry Gritz
[email protected]
_______________________________________________
Oiio-dev mailing list
[email protected]
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
