[NTLUG:Discuss] Re: Need some inputs on porting.

[Vaidya, Harshal (Cognizant)]

Oh God!! This reminds me of another problem which we may face if we are
to port the code. If Rougewave is doing a lot of serialization in its
internal code, it could cause havocs while porting the code from 32 to
64 bit compatibility. If the serialization is on the wire types, I think
it shouldn't be a problem if they are doing it on a persistent store
like a file then we might get into depp shit!!

What do you think? 

-----Original Message-----
From: Chris Cox [mailto:cjcox at acm.org] 
Sent: Wednesday, October 01, 2003 8:41 PM
To: NTLUG Discussion List
Subject: Re: [NTLUG:Discuss] Re: Need some inputs on porting.


Vaidya, Harshal (Cognizant) wrote:
...
>>>problems with their class libraries. (when I worked at Sabre in 1995)
Uh.................................................................^^^^^


> 
> 
> 
> We have the source code for these tools too. Can you tell me in detail

> as to what did you fix in these libraries. We might consider doing it 
> too.
> 

Our problem was with the serialization routines.  We smashed objects to
go across the wire in a portable fashion (we wrote our own orb... back
in the days when orbs were the thing).

I really, really don't remember the changes we made.  Honest. However,
we did work with Rogue Wave, so it's likely that our changes, or
something like our changes, made it into future versions of their
product (not sure who owns that technology now though).


_______________________________________________
https://ntlug.org/mailman/listinfo/discuss
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: InterScan_Disclaimer.txt
Url: http://ntlug.org/pipermail/discuss/attachments/20031002/cedc6c46/InterScan_Disclaimer.txt