perl - $_ outputting extra bit of data -


the static $_ might needs flushed. tried done $|=1;.

enter image description here

desired output:

client

connected server. sent server : sas4 sent server : 50 sent server : sas_action login sent server : login bss sent server : password cleint sent server : $end$ message received server : sas4 message received server : 61 message received server : sas_action login_ack message received server : ack_status 0 message received server : ack_message logged in message received server : $end$

server

waiting client. connected : 127.0.0.1, port : 1862 message received client : sas4 message received client : 50 message received client : sas_action login message received client : login bss message received client : password cleint message received client : $end$ server client : sas4 server client : 61 server client : sas_action login_ack server client : ack_status 0 server client : ack_message logged in server client : $end$

code :

client 

use strict; use warnings; use io::socket::inet;  $socket = new io::socket::inet (peerhost => '127.0.0.1', peerport => '1055', proto    => 'tcp', reuse    => 1) or die "$!\n";  print "connected server.\n";  send_login(); $|=1; receive_loginack(); $socket->close();  sub send_login {     $login_txt = "login.txt";     open login, '<', $login_txt or die "cannot open $login_txt $!\n";     @login = <login>;     close login;      $logfile = "logfile.txt";     open log, '>>', $logfile or die "cannot open $logfile ($!)\n";      foreach $login (@login)     {         print $socket $login;         print log "client : $login";         print "sent server : $login";         #last if ($login eq "\$end\$\n");      }     close log; }  sub receive_loginack {     while (<$socket>)     {            print"message received server : $_";     } }

server

use strict; use warnings; use io::socket::inet;  $socket = new io::socket::inet (localhost => '127.0.0.1', localport => '1055', proto => 'tcp', listen => 1, reuse => 1) or die "oops: $! \n";  print "waiting client.\n"; server_loop(); $socket->close();  sub server_loop { outer:     while (my $clientsocket = $socket->accept())     {         print "connected : ", $clientsocket->peerhost();         print ", port : ", $clientsocket->peerport(), "\n";  inner:         while (<$clientsocket>)                                 #         {                                                       #             print"message received client : $_";           #             last inner if ($_ eq "\$end\$\n");                  #       receiving             #last outer if ($_ eq "\$quit\$\n");                #             print $clientsocket $_;                             #         }                                                       #          $login_ack = "login_ack.txt";         open loginack, '<', $login_ack or die "cannot open login acknowledgment file $login_ack ($!)\n";         @loginack = <loginack>;         close loginack;          $logfile = "logfile.txt";         open log, ">>", $logfile or die "cannot open $logfile ($!)\n";          foreach $loginack (@loginack)         {             $|=1;             print $clientsocket $loginack;             print log "server : $loginack";             print "server client : $loginack";             #last if ($loginack eq "\$end\$\n");         }          close log;         close $clientsocket;     } }

the server's input loop contains:

print $clientsocket $_;

so client sends server being sent client, before login_ack.txt file. client prints message received server.


Comments

Post a Comment

Popular posts from this blog

Why does Ruby on Rails generate add a blank line to the end of a file? -

running rails generate controller foo home results in: class foocontroller < application controller def home end end (there's nothing on line in actual file, blank line) is there purpose blank line? it's common use newline indicate end of line, last line. many editors (like vi, use) add in newline silently. consensus text files (especially in unix world) should end in newline, , there have been problems historically if wasn't present. why should text files end newline? the tool used count lines in file "wc" counts newlines in file, without trailing newline show 3 instead of 4. it improves readability of templates used in generator. consider: https://github.com/rails/rails/blob/master/railties/lib/rails/generators/rails/controller/templates/controller.rb to remove trailing newline, template have last line of: end<% end -%> instead of: end <% end -%> that seems less readable me. the discussion below refers
Read more

keyboard - Smiles and long press feature in Android -

i've created android keyboard. how add features inserting smilies, , using long keypresses display symbols? to create long-press behavior allows select several options pop-up menu, follow guide (specifically pop-up menu section): http://developer.android.com/guide/topics/ui/menus.html smileys (also known emoticons) combination of keys, understood programs , parsed same way. have do, when clicks smiley face on keyboard, simulate pressing of key combination matching emoticon. example, when clicks smiley, should simulate key presses ':' , ')' :). here's list of emoticons: http://en.wikipedia.org/wiki/list_of_emoticons
Read more

node.js - Bad Request - node js ajax post -

i'm using express 3.0 , node v0.11.0. have button submits form , i'm using ajax post data json object node server. client code is: $('#contact').submit(function(e) { console.log('submit called'); var formdata = json.stringify($('form').serializeobject()); console.log(formdata); $.ajax({ url: "http://localhost:3000/savedata/", type: "post", datatype: 'json', data: {objectdata: formdata}, contenttype: "application/json", complete: function() { console.log('process complete'); }, success: function(data) { console.log('process sucess'); }, error: function() { console.log('process error'); }, }); return false; }); then on server: var express = require('express'); var app = express(); app.set('views', __dirname + '/views'); app.set('view engine', 'jade'); app.use(express.bodyparser());
Read more