DO bug?

[pmougin at acm.org (Philippe Mougin)]

So far I've not experienced the problem you describe with DO. Are you 
sure the problem comes from DO? Some APIs use the % character in a 
string as a meta character. Are you sure your string, once transfered 
with DO, is not used at some points with such APIs? To eliminate or 
confirm a DO related problem, could you run the same test with a string 
(containing %) created locally (i.e. not obtained from DO)?

Best,

Philippe Mougin

 > I've experienced some pretty annoying DO behaviour. When
 > transferring objects containing strings with %'s some mechanism
 > deep within the DO architecture crashes horribly.  The string is
 > accepted in the remote object and the set-method executes fine
 > but it seems like some DO cleanup really don't like such strings.
 > Strings without %'s works fine. It's not to difficult to work around 
it,
 > but a bit annoying. But, it could of course be something stupid I do,
 > have any others here experienced this?
 >
 > Regards
 > Kjetil Husveit