With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.
The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community
Your Input Matters Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.
If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.
Ok, PERL gurus! I am working on a project to allow streaming(scrolling) text for a cgi chat server in a multi-framed HTML document. I have seen several client / server models and sample code, but cannot seem to get it straight. The problem I see with many of the sample daemons is that they create way too much server load. ex. The have to spawn a child process to communicate with a newly opened socket. I need a server to accept incoming sockets and to print messages recieved from a socket to all other open connections from ONE process(I guess this would be similar to the innd process). I will be INCREDIBLY grateful for some advice as this is an extremely important feature for me to add. Thank you very much.
------ Text Omitted .... Code needing fixed is listed below
I feel the code is almost there, but it has bugs in it. I've set the server to listen on a particular port. Rather then writing the client, I've just telneted in to test the response. Once the socket is opened, I type in data(then of course the steam will be ended via a \n) and the data is sent back to my socket and it is then closed. For some reason the text is not being broadcasted to other open connections. I'd really appreciate further help if it is possible. Also, once completed this version should be able to support up to and even beyond 50 - 100 simultaneous users. Is this feasable with this implementation. Here is my code so far. Also The cgi web-based interface will be in a 3 frame window. The upper left frame will recieve all new text written by other chatters. The lower frame will allow the user to add new text, which will in turn be sent to the upper right frame. The third frame will be used for customizable options. Thank you greatly! - Eric
socket(LISTEN, $AF_INET, $SOCK_STREAM, $proto) || die "socket: $!"; bind(LISTEN,$this) || die "bind: $!"; listen(LISTEN,5) || die "connect: $!";
select(LISTEN); $| = 1; select(stdout);
print "Listening for connections....\n";
while (1) { # each time, create the select bit array $bits = 0; for (@CLIENTS) { vec ($bits, fileno ($_), 1) = 1; } vec ($bits, fileno (LISTEN), 1) = 1;
#OK, wait until something comes in. $nfound = select($rbits=$bits,undef,$ebits=$bits,undef);
#OK, something woke us up. # see if it is a new connection... if (vec($rbits, fileno(LISTEN), 1)) { # new connection accept (NS, LISTEN); push (@CLIENTS, NS); }
#no, try the clients $incoming = undef; for (@CLIENTS) { if (vec ($rbits, fileno ($_), 1)) { #OK, this client's got something, read a line... $incoming .= <$_>; } }
# next, send $incoming to all clients... if ($incoming) { for (@CLIENTS) { print $_ "$incoming\n"; } } }
Using the -w flag says: Unquoted string "stdout" may clash with future reserved word at line 24. Name "main::ebits" used only once: possible typo at line 37. Name "main::NS" used only once: possible typo at line 43. Name "main::nfound" used only once: possible typo at line 37.