Yahoo, I figured it out!!! I did indeed need the global variable $abort, but
another
problem crept in. Long and the short of it is that when you abort a transfer,
the socket
gets closed at the same time, and after my loop I had a $sock->close(). My
application
froze here (I will investigate furt
Harald,
| If the Abort routine intervenes and invalidates $data,
| the next read finds an invalid pointer or, worse, a pointer to an invalid
| buffer.
That's the key thing. How to stop the routine from reading data once and for
all. Even
when I close the connection between the two handles it cont
| -Original Message-
| From: Morbus Iff [mailto:[EMAIL PROTECTED]
|
| Ok. I have no clue what I'm talking about.
Welcome to the club ;-)
| to a friend, who has done VB stuff in the past, but nothing
| with Perl GUI's.
Takes some getting used to. Goes for both VB and Win32-GUI. Transition
Ok. I have no clue what I'm talking about.
I created AmphetaDesk:
http://www.disobey.com/amphetadesk/
Roughly, it includes a built in webserver that listens until "quittin'
time" for requests on port . It writes out logging information to
STDOUT, which makes a pretty console window.
| The problem I believe is because since my application is GUI
| and event driven(OOP), any
| action one place jumps you to another section of code,
| without knowing how to get back and
| say, "hey stop doing that, move on". Does this make sense?
I guess you're right, it is about multitasking.
Harald said:
| 1) instead of close, move the file pointer to eof
| seek FILE, 0, 2;
| so that the read fails without dying
This can't be, because the reading is from a socket not a file. I'm reading
from a socket
and writting to a file (in blocks of 10240 bytes). The read does stop when I
abort
6 matches
Mail list logo
