From: Vince Forgetta <forgetta@...>
Date: 2008-04-15T03:22:52+09:00
Subject: Re: help need in chat client/server

------=_Part_2324_7220197.1208197365681
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi HadsS,

There is some example code in Peter Coopers book (Beginning Ruby From Novice
to Professional):

http://www.springerlink.com/content/ph5611n3q3uu0619/

Not sure you'll have access to it.  I can forward you the chapter if you
like.

I am working on some network programming in ruby as well.  Maybe we can
collaborate a little.  It's not the easiest thing to grasp :(

Vince

On Mon, Apr 14, 2008 at 2:13 PM, Glen Holcomb <damnbigman@gmail.com> wrote:

> On Mon, Apr 14, 2008 at 11:25 AM, HadsS <a.hadss@gmail.com> wrote:
>
> > Hey...
> > Im new to this network programmin and I need help with this code i
> > copied and changed a little.
> > this is a client/server chat..
> > -----------------------
> > Server code:
> >
> > require "socket"
> > PORT = 12321
> > server = TCPServer.new(PORT)
> > flag=true
> > while (session = server.accept)
> >  while flag==true
> >  print "Sending:"
> >  line=gets.chomp!
> >  session.puts line
> >  end
> > end
> > ----------------
> >
> > Client Code:
> > require "socket"
> >
> > PORT = 12321
> > HOST = ARGV[0] || "localhost"
> > flag=true
> > session = TCPSocket.new(HOST, PORT)
> > while flag==true
> > line = session.gets
> > puts "Recived:#{line} "
> > end
> > ---------
> >
> > i dont know what i did but its sort of doing a one way communication..
> > can someone please help me with creating two clients and making them
> > chat 2way amongst them..
> > please.. i would really be thankfulll
> > waiting for a reply
> >
> >
> There are a few logical/structural problems here:
>
> Firstly, it is only one way because one end is sending and the other
> listening but the sending end never listens and the listening end never
> sends.
>
> Secondly, control in this is going to be painful as it is.  You probably
> want to thread your program so that each end can "talk" and "listen" at
> the
> same time.  You could make it clunky and just switch between the two but
> that would be rather un-intuative.
>
> I would offer up some sample code but haven't done any socket programming
> in
> Ruby and am currently at work  I bet someone will come along with more
> useful info though (I offer this as something to get you going in the
> right
> direction until then).
>
> --
> "Hey brother Christian with your high and mighty errand, Your actions
> speak
> so loud, I can't hear a word you're saying."
>
> -Greg Graffin (Bad Religion)
>

------=_Part_2324_7220197.1208197365681--