Re: Tk & Socket: Tk::Error: fileno not same for read X and write Y

I don't get that error under Windows using ActivePerl (5.8.0, Tk 800.024) but the code still does not work correctly. I'll try and test it under RedHat 9 later.

The problem that I ran into is that, as pg pointed out, accept blocks. I also had the problem that the listening socket always triggers the readable event, whether a client is connecting or not. You can get around accept blocking by using select, but, then, why bother using fileevent at all? And since it appears to have issues, you'll probably be better off writing your own select code to poll the listening socket for data, and possibly the client socket as well.

bbfu
Black flowers blossom
Fearless on my breath

Comment on Re: Tk & Socket: Tk::Error: fileno not same for read X and write Y Select or Download Code

Replies are listed 'Best First'.
Re: Re: Tk & Socket: Tk::Error: fileno not same for read X and write Y by dotsha (Initiate) on Oct 15, 2003 at 07:20 UTC
(I'm the original poster of the question above -- sorry, didn't notice I wasn't logged in when I pressed save.) pg: Yes, as bbfu guessed, the code I posted is a test-case to show the problem. Originally, my program read a number of sensors and then distributes the data out over sockets to multiple clients. As some of the sensors are accessed using TCP as well, the program needs to act as a socket server AND a socket-client at the same time. I therefore wrote everything around a select() in perl since I can't afford anything to block in the program. That program works fine. Recently, I've needed to do a simulator for the system, whereby instead of reading data from sensors and distributing it out to clients, an operator would be able to control the values on-the-fly. So I am migrating the original program into a Tk environment with a dynamic GUI front-end. As Tk has a select() at its heart, and that select() can be tapped into using fileevents, the overall model should not be much different from my original program. bbfu - I tried running it under Window and found the same problem of accept() blocking. Strange -- Under Redhat, the listening socket is not "readable" until a client connects, and only then does it pass control to the server_read() function, and so accept() doesn't block. My original program is able to handle multiple events without blocking. Even the Tk version on Linux works fine -- the GUI is operational and doesn't block. It only bombs with the error above when I try to set a "writable" fileevent on the client socket ... even then the MainLoop is still active and the GUI and other events go on fine (multiple clients can still connect).	[reply]

Replies are listed 'Best First'.

Re: Re: Tk & Socket: Tk::Error: fileno not same for read X and write Y
by dotsha (Initiate) on Oct 15, 2003 at 07:20 UTC

pg: Yes, as bbfu guessed, the code I posted is a test-case to show the problem.

Originally, my program read a number of sensors and then distributes the data out over sockets to multiple clients. As some of the sensors are accessed using TCP as well, the program needs to act as a socket server AND a socket-client at the same time. I therefore wrote everything around a select() in perl since I can't afford anything to block in the program. That program works fine.

Recently, I've needed to do a simulator for the system, whereby instead of reading data from sensors and distributing it out to clients, an operator would be able to control the values on-the-fly. So I am migrating the original program into a Tk environment with a dynamic GUI front-end. As Tk has a select() at its heart, and that select() can be tapped into using fileevents, the overall model should not be much different from my original program.

bbfu - I tried running it under Window and found the same problem of accept() blocking. Strange -- Under Redhat, the listening socket is not "readable" until a client connects, and only then does it pass control to the server_read() function, and so accept() doesn't block. My original program is able to handle multiple events without blocking. Even the Tk version on Linux works fine -- the GUI is operational and doesn't block. It only bombs with the error above when I try to set a "writable" fileevent on the client socket ... even then the MainLoop is still active and the GUI and other events go on fine (multiple clients can still connect).

[reply]