ibm sez yes it's supported. we'll give it a whirl. will update with highlights.
--- Post updated at 11:16 ---
Quote:
Originally Posted by
zxmaus
well endianness only matters for binary data not text data. If I understand you correctly you want to transfer text data only so that should work fine. If you however need something runnable you would need to run it through a converter and recompile.
ibm suppt said that replication does the same ops on the recipient that were done on the originator to effect the change in the first place. which says to me all the data sent in replication must be text, I'll check that with tcpdump when I get time. I suspect it falls down on binary blobs like image data/video saved in attributes, but we don't have any of those so we don't care. Passwords might be fun too but OTOH those have their own handling including cryptosync, so I expect they're correct.
In general, my reading (is it correct ?) of this is that it's about correct layer6 implementation, and Sun took care of that over 30 years ago with XDR for RPC, later standardized into the notion of network byte order.
Editorial Comment:
|
so WTF isn't this implemented correctly like everywhere? I know, development resources. IBM was always careful about this up until the bugly edges where they went into the weeds sometimes, but were responsive when bugs were found. Heard from a colleague that another (newer) non-IBM package didn't replicate right cause their flaming binary index wasn't handled right across platforms. Seriously ?
|
|
that was cool, I made my own editorial tags and whaddya know, someone had implemented them. who knew...