Return-Path: Mailing-List: contact soap-user-help@xml.apache.org; run by ezmlm Delivered-To: mailing list soap-user@xml.apache.org Received: (qmail 34766 invoked from network); 15 Jan 2002 18:29:29 -0000 Received: from mail.gmx.net (213.165.64.20) by daedalus.apache.org with SMTP; 15 Jan 2002 18:29:29 -0000 Received: (qmail 25697 invoked by uid 0); 15 Jan 2002 18:29:28 -0000 Received: from p50830fcc.dip.t-dialin.net (HELO gmx.de) (80.131.15.204) by mail.gmx.net (mp002-rz3) with SMTP; 15 Jan 2002 18:29:28 -0000 Message-ID: <3C4474FF.2020709@gmx.de> Date: Tue, 15 Jan 2002 19:29:19 +0100 From: Alex Rau User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.7) Gecko/20011226 X-Accept-Language: en-us MIME-Version: 1.0 To: soap-user@xml.apache.org Subject: Re: Multithreading and Blocking of Deployed Services References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi Jason, we did a major code rewrite last night. Mainly we moved the gui and broadcast stuff into the service class. This way we saved a lot of soap requests. Another issue was our servlet container, which we manipulated for debugging purposes and started to fail to server multiple requests in parallel. After this code rewrite our system worked without deadlocks. Today we ran it on 2 ipaqs and one notebook and tested our first information dissemination algorithms :) When i said, the service interface would call it self via soap, i did a mistake. It was calling the other clients service interface. But the idea of writing a complete web application instead of simple service interface and a "normal" application holding the servlet container did help (reduced bandwidth and error detection :) ). Tnx a lot, Regards Alexander Rau PS: Anyone offering an intership for a computer science graduate student from germany for about 3-6 (or even more) months in the sf bay area ?