From mint-bounce@lists.fishpool.fi Sat Apr 30 16:18:24 2005 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Subject: Re: [MiNT] question about socket calls From: Odd Skancke Reply-To: ozk@atari.org To: mint@fishpool.com In-Reply-To: References: Content-Type: text/plain; charset=UTF-8 Date: Sat, 30 Apr 2005 16:15:03 +0200 Message-Id: <1114870504.5602.34.camel@fedora> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-2) X-MIME-Autoconverted: from 8bit to quoted-printable by smtp210.tiscali.dk id j3UEH4GJ070234 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: ozk@atari.org Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: X-Virus-Scanned: by amavisd-new at relay.boerde.de X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on relay.boerde.de X-Spam-Status: No, hits=1.7 tagged_above=-50.5 required=7.0 tests=AWL, BAYES_00, RCVD_IN_SORBS X-Spam-Level: * Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by wh58-508.st.uni-magdeburg.de id j3UEIOlp010265 lør, 30,.04.2005 kl. 09.39 -0400, skrev Lonny Pursell: > on 4/30/2005 1:09 AM, Frank Naumann wrote: > > > No, this is not a kernel task. But we can made a SLB wrapper around the > > mintlib DNS lookup. This should not be complicated. > > That would work. Not having to rely on gluestik for resolve would be quite > ok. I don't know anything about XDD as ozk suggested, but either way if one > can unload gluestik, that would be very good. > > I have done some testing with the socket calls, and seems to work quite > nicely as I can communicate with the vnc server. The only problem I have > atm is the event loop. The program must have a proper event loop for the > window management. What is the best/fast way to poll a socket to see if some > data is waiting? The best way.... hmm... tell me you use XaAES, I'll add fselect to evnt_multi() and all your probs are solved :) best regards, Odd Skancke