Cesar,

Sometimes rewriting is exactly the right thing to do.  For example, Object Arts 
wrapped the Microsoft XML library.  First, there is the question of untrusted 
input and MS binaries (yikes!!!), but also, any time bad input went into it, it 
would fire off an error with no indication of where it got into trouble.  For 
some reason, MS did not think to take an IStream pointer that would have 
allowed one to check the position.

For an http client, OA again wrapped MS binaries, complete with the typical 
punishing timeouts under MS control, and being hobbled if IE had been set (or 
set itself) to work offline.

Dolphin is a wonderful product, but users would have been better served with 
home-grown code in those cases.

Bottom line: I think we should rewrite when it makes sense to do so, and wrap 
just about anything that makes sense for interoperability.  Clearly there is a 
lot to wrap, and priorities must be set, as it will often fall on an individual 
to do the dirty work.  SSL is a no-brainer.

Bill


-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of 
[email protected]
Sent: Wednesday, December 30, 2009 8:59 PM
To: [email protected]
Subject: Re: [Pharo-project] Developer guide ... ?

Bill,

I think you nailed it precisely!  Although all 'systems' working in Pharo will 
not be enough if we cannot connect and integrate with the leading technologies 
that we cannot afford to displace/emulate/write in Pharo smalltalk.

--
Cesar Rabak
 
 

Em 30/12/2009 22:54, Schwab,Wilhelm K <[email protected]> escreveu:


Levente,

I'll give you a pass on RPC, on SOAP for sure, and _almost_ on CORBA :)  
However, a culture of dismissing important things as crap lead us to a point 
approaching 15 years into Squeak's existence where it does not have ready 
access to SSL.  I know about stunnel, but that is more cheat than fix.  Pharo 
needs to embrace the worthy or we will still be on the fringe 15 years from 
now, and that would be tragic.

Bill

_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to