🚀 go-pugleaf

"Alan Shiers" <ashiers@hfx.eastlink.ca> wrote in message
news:3D24D4AC.1B1BFBBC@hfx.eastlink.ca...
> Hi there,
>
> >Owen wrote:
> >If you post your entire uploadFile() method (if its not too huge), it
will be easier to see what's happening.
>
> >hth
> >Owen
>
> Sure, I'll provide you with the method receiveFile() which is on the
> server-side app and uploadFile() which is on the client-side app.  Also,
> I'll include my request_workerThread class that you might see how I'm
> trying to
> split the proceedure on the client-side app.  I've been working on the
> request_workerThread class and have solved the "Bad descriptor file"
> problem.
> All I had to do was instantiate the FileInputStream object there
> instead.

Alan,

Just to let you know that I am on it, but I'm juggling things a bit here, so
it'll be as and when :)

From a first glance the problem /may/ be on the client side, but it's not so
easy to see what's going on; the various responsibilities of the classes
don't seem to be too strictly bounded, which makes things harder to follow -
I'll crack it though ;)

Just a thouht, but is allowing the thread that's actually uploading to be
suspended a good idea when its performing what amounts to socket IO? It
strikes me that if you're going to allow pausing (why do you need it?),
there should be a way of signalling this to the server, perhaps in the same
way that FTP uses control messages (on a different socket).

I'll be back...

Owen