Xref: utzoo comp.sys.mac.programmer:22565 comp.protocols.appletalk:5475
Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!rpi!batcomputer!llenroc!cornell!vax5.cit.cornell.edu!ywc
From: ywc@vax5.cit.cornell.edu
Newsgroups: comp.sys.mac.programmer,comp.protocols.appletalk
Subject: Re: ADSP transmission delays
Message-ID: <1991Mar12.124904.3305@vax5.cit.cornell.edu>
Date: 12 Mar 91 16:49:04 GMT
References: <0B010004.pes6bq@outpost.UUCP>
Distribution: comp
Organization: CIT, Cornell University
Lines: 36

In article <0B010004.pes6bq@outpost.UUCP>,
peirce@outpost.UUCP (Michael Peirce) writes:
> I've been playing around with ADSP lately.  Things are working fairly
> well - ADSP sets up the connection and sends data back and forth just
> fine.
>
> My problem is that I'm trying to track a mouse drag on a remote machine.
> So as I'm dragging the mouse I send the mouse delta's over ADSP.
> The problem is that these seem to get buffered up on the sending machine
> while the mouse is down.
>
> This doesn't happen all the time, some seem to get out, but the majority
> show up on the remote machine after quite a bit of time (relatively
> speaking).
>
> The data does eventually get through, but not close enough to real
> time for my purposes - oftne MANY seconds.
>
> This is running on LocalTalk, but there is no other network activity
> on this net (located in my house).  I'm setting eom = 1 & flush = 1
> for each chunk of data that I write.  My send and receive buffers
> are both 1K.
>
> Anyone have any ideas what's going on?  I'd appreciate any insights
> you might have into this behavior.
>
> -- michael
>
> P.S.  Please don't tell me I have to go back to ATP to get "real time"
> network performance...
>
>
> --  Michael Peirce         --   outpost!peirce@claris.com
> --  Peirce Software        --   Suite 301, 719 Hibiscus Place
> --  Macintosh Programming  --   San Jose, California 95117
> --           & Consulting  --   (408) 244-6554, AppleLink: PEIRCE