Hello everyone!
I've got a distributed object that inherits from co::Serializable. This
objects serializes a few kilobytes of data all at once, which is then pushed
to slave instances. No subsequent commits happen to that object.
Everything was working fine and dandy with previous versions of EQ (this is
actually code that's barely been touched in two years or so). Recently, I
pulled from the eyscale repos to the latest versions of all the libraries
(Collage commit: 378ab5c677c8bfd0a7e8614fe73c158eb6357a65).
Now I'm noticing the following behavior. If i commit less than 600-700 bytes
of data, everything works fine. However, if I serialize more than that, I
get a bunch of errors within co::fdConnection ("Invalid argument (22)",
"Error during write after 0 bytes, closing connection", etc).
Is this related to issue
https://github.com/Eyescale/Collage/issues/40 ?
Overriding getChangeType() on my distributed object and setting it to
co::Object::UNBUFFERED doesn't seem to be helping...
Thanks in advance :),
Harris
--
View this message in context:
http://software.1713.n2.nabble.com/Issue-with-co-serializable-in-recent-Collage-version-tp7585328.html
Sent from the Equalizer - Parallel Rendering mailing list archive at Nabble.com.
_______________________________________________
eq-dev mailing list
eq-...@equalizergraphics.com
http://www.equalizergraphics.com/cgi-bin/mailman/listinfo/eq-dev
http://www.equalizergraphics.com