With regards of your question about LDAP, if your expected result set is over 50 entries, add an or: block to check for result code == 4 in LDAP-Core class LDAPResult checkForExceptions (resultCode = 0 or: [resultCode = 4] or: [resultCode = 5] or: [resultCode = 6]) ifFalse: [ | ex | ex := LDAPException newWithCode: resultCode. ex signal: (errorMessage ifEmpty:[ex messageText]) ] -----Mensaje original----- De: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr]En nombre de Schwab,Wilhelm K Enviado el: Viernes, 14 de Agosto de 2009 03:35 p.m. Para: Pharo-project@lists.gforge.inria.fr Asunto: [Pharo-project] Networking - how much experience/testing ishappening? Hello all, Are any of you doing extensive networking with Pharo? IMHO, Seaside connections to a local copy of apache does not really count, since it won't be as likely to see dropped connections and other challenges. I ask because I have LDAPlayer talking to UF's server, and had Pharo lock up something awful. This was over a pre-production vpn connection from home, and on a not-really-supported 64 bit system tricked into running the 32 bit client. I'm not sure how stable all of that is. Still, I had to dust off the end-process button; cmd-. brought up debuggers, but those were unresponsive too. Andreas Raab mentioned a snag with LDAPlayer not reacting well to network errors, so that might have been the problem. Still, I can see the ldap worker thread going nuts, but the UI thread??? If it's a fluke, fine; if this happens in real use, we have a problem. Bill _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Internal Virus Database is out-of-date. Checked by AVG. Version: 7.5.560 / Virus Database: 269.21.6/1323 - Release Date: 10/03/2008 11:07 a.m.