Re: getting socket identification numbers

2001-01-03 Thread Sivakatirswami

 If you are going one-on-one, then you can just have the stack show
 your id, and use a different method (email, etc) to communicate that
 to the target.
 
 "different method" (to get the IP)  which we once used with the now defunct
Marionette (4 years ago) that DID rely on a known third server but very
"lightly" was:

Initiating chatter box "server" boots, logs onto the net and writes it's
(dynamically received) IP to a small text file at some known ISP host
machine's web site, containing nothing but it's IP,port, then goes into
listen mode.

"Client" side chatters boot up, uses http to get the unknown chat server's
IP sitting on the known ISP web site,  and then starts talking directly to
the initiating chat machine. You can build on this to set up a "chat room"
that is not happening on any ISP's server. . .the ISP's server just serves
up the IP address of the chat server.

The initiating chatter box has a field that serves as the "chat room" and
users get that data fed back to them after each post. which is appended to
the field. The strategy worked like a charm, but Marionett's protocols were
horrifically slow and the app had a memory leak and kept locking up after
opening more then three sockets to chatters, we abandoned the whole project.
But this should blaze in MC. Some "traffic control" would be needed for a
full blown chat room.


 If you are looking for a more universal/large scale/robust/automatic
 system, then I would think you'd need to set up a server at a fixed
 address (in other words, not at your location) and set up the chat
 clients to automatically log in to the server, and find each other
 through that.

Hinduism Today

Sivakatirswami
Editor's Assistant/Production Manager
www.HinduismToday.com
www.HimalayanAcademy.com
[EMAIL PROTECTED]


Archives: http://www.mail-archive.com/metacard@lists.runrev.com/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to [EMAIL PROTECTED], not this list.




Re: getting socket identification numbers

2001-01-02 Thread Mark Talluto

on 1/2/01 3:10 PM, [EMAIL PROTECTED] at
[EMAIL PROTECTED] wrote:

 I'm working on a chat program, bolstered by the help
 of others on the list. I want to get the IP address of
 the person chatting with me, even if they don't know
 how to get it themselves. I investigated hostAddress
 and peerAddress but ran into a puzzle -- can anyone
 explain it?

I have looked into this again and have found that:

put peerAddress(s) into field "whatever"

will also get the other person's ip number.  This is much cleaner than the
other way I just posted.  The key for us newbies is to understand that the
"s" variable is the part that we miss.  You must use the variable that you
chose at the beginning of the handler that does the reading.  For example, I
used this:  

on openCard
  put field "port" into iPort
  accept connections on port iPort with message "newconnect"
end openCard

on newconnect s
  --FIGURE OUT THE LENGTH OF THE MESSAGE
  read from socket s for 1 line
  put it into tLength
  
  --NOW READ FOR THE SPECIFIED LENGTH OF THE MESSAGE
  read from socket s for tLength
  
  put peerAddress(s)
...
...
end newconnect

-Mark Talluto


Archives: http://www.mail-archive.com/metacard@lists.runrev.com/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to [EMAIL PROTECTED], not this list.




Re: getting socket identification numbers

2001-01-02 Thread Mark Talluto

on 1/2/01 3:10 PM, [EMAIL PROTECTED] at
[EMAIL PROTECTED] wrote:

 I'm working on a chat program, bolstered by the help
 of others on the list. I want to get the IP address of
 the person chatting with me, even if they don't know
 how to get it themselves. I investigated hostAddress
 and peerAddress but ran into a puzzle -- can anyone
 explain it?

I have just implemented that feature.  This is what I did.

 --FIGURE SENDERS IP ADDRESS
  set the itemdel to "|"
  put item 1 of s   " " into field "whatever"

The s variable contains the other person's ip information.  This should be
placed somewhere after the read command.  I think it must be in the same
handler as the read command though.

Hope this helps some.

-Mark Talluto

 
 I'm chatting on my Win98 machine between two stacks
 with different addresses, 208.193.15.192 given to me
 by the ISP, and 127.0.0.1, the loopback address. In
 each stack I have a button with this script:
 
 on mouseUp
 put fld "sendIPfld" into vIP
 put fld "sendSocketFld" into vSocket
 put vIP":"vSocket into tDest
 open socket tDest
 put hostAddress(tDest)returnpeerAddress(tDest)
 into fld resultFld
 close socket tDest
 end mouseUp
 
 From each stack I get the same result -- the
 hostAddress and the peerAddress are the same, and that
 address is for the stack that I am connecting to, not
 the address for the stack with the button. Shouldn't
 they be different?
 
 I'm using two different port numbers -- one to go from
 the 208.193.15.192 address to the 127.0.0.1 address,
 and one to go back the other way. But I don't see how
 that could make any difference.
 
 Any help would be much appreciated. Michael Kann,
 
 [EMAIL PROTECTED]


Archives: http://www.mail-archive.com/metacard@lists.runrev.com/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to [EMAIL PROTECTED], not this list.




Re: getting socket identification numbers

2001-01-01 Thread andu


This is a multi-part message in MIME format.

--=_NextPart_000_0034_01C0740A.EED97EA0
Content-Type: text/plain;
   charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I do not have a permanent domain id. I can get a temporary one and set =
up my mc server from my home pc, but the id #s change every time I log =
on.  Is there a simple way for MC to initiate and identify these numbers =
for use in chat stacks etc.?

Thanks

Peter

I would be greatful if you sent your mail as plain text.

After you do: open socket X, do: put hostAddress(X) into myAddress ##your current IP
address.

Regards, Andu 
___
[EMAIL PROTECTED]

Archives: http://www.mail-archive.com/metacard@lists.runrev.com/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to [EMAIL PROTECTED], not this list.




Re: getting socket identification numbers

2001-01-01 Thread Geoff Canyon

At 3:53 PM -0500 1/1/01, Sound Medicine, Inc. wrote:
I do not have a permanent domain id. I can get a temporary one and 
set up my mc server from my home pc, but the id #s change every time 
I log on.  Is there a simple way for MC to initiate and identify 
these numbers for use in chat stacks etc.?

If you are going one-on-one, then you can just have the stack show 
your id, and use a different method (email, etc) to communicate that 
to the target.

If you are looking for a more universal/large scale/robust/automatic 
system, then I would think you'd need to set up a server at a fixed 
address (in other words, not at your location) and set up the chat 
clients to automatically log in to the server, and find each other 
through that.

Regards,

Geoff

Archives: http://www.mail-archive.com/metacard@lists.runrev.com/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to [EMAIL PROTECTED], not this list.




Re: getting socket identification numbers

2001-01-01 Thread michael kann

I'm working on a chat program, bolstered by the help
of others on the list. I want to get the IP address of
the person chatting with me, even if they don't know
how to get it themselves. I investigated hostAddress
and peerAddress but ran into a puzzle -- can anyone
explain it?

I'm chatting on my Win98 machine between two stacks
with different addresses, 208.193.15.192 given to me
by the ISP, and 127.0.0.1, the loopback address. In
each stack I have a button with this script:

on mouseUp
  put fld "sendIPfld" into vIP
  put fld "sendSocketFld" into vSocket
  put vIP":"vSocket into tDest
  open socket tDest
  put hostAddress(tDest)returnpeerAddress(tDest)
into fld resultFld
  close socket tDest
end mouseUp

From each stack I get the same result -- the
hostAddress and the peerAddress are the same, and that
address is for the stack that I am connecting to, not
the address for the stack with the button. Shouldn't
they be different?

I'm using two different port numbers -- one to go from
the 208.193.15.192 address to the 127.0.0.1 address,
and one to go back the other way. But I don't see how
that could make any difference. 

Any help would be much appreciated. Michael Kann, 

[EMAIL PROTECTED]



__
Do You Yahoo!?
Yahoo! Photos - Share your holiday photos online!
http://photos.yahoo.com/

Archives: http://www.mail-archive.com/metacard@lists.runrev.com/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to [EMAIL PROTECTED], not this list.