egghelp/eggheads community

help with sock connections

2001-10-31T03:17:00-04:00

From the tcl command manual page you read:

In the first form, the read command reads all of the data from
channelId up to the end of the file.

I think that pretty much explains the problem... you are trying to read all the data from the socket up to the end of file... for a socket, that means until the connection is closed. So it's going to freeze until the socket is closed, which may be quite a while.

Your whole script is designed wrong. You need to use nonblocking sockets (read 'fconfigure') and file events (read 'fileevent') to do this.

Statistics: Posted by stdragon — Wed Oct 31, 2001 3:17 am

help with sock connections

2001-10-30T16:31:00-04:00

Is there no better way to read a socket?
When the sock is open the eggdrop do not response

Code:

 while {[validsock $sock]} {  set text [read $sock]  msn:putchan "user" "$text"  putlog "msn: $text"  if {[lindex $text 0] == "BYE"} {   close $sock   }}proc validsock {channel} {return [expr 1 - [catch "fconfigure $channel"]]}

Statistics: Posted by Guest — Tue Oct 30, 2001 4:31 pm

help with sock connections

2001-10-30T16:15:00-04:00

Yes I read http://dev.scriptics.com/man/tcl8.3/TclCmd/read.htm

And I always do set $text "lala"
stupid me

Statistics: Posted by Guest — Tue Oct 30, 2001 4:15 pm

help with sock connections

2001-10-30T15:09:00-04:00

You don't use the $ symbol in a set command.

Follow the links in one of my previous posts, it has a link for information on the read command, and tells you how to use it to read a certain amount of data.

Statistics: Posted by ppslim — Tue Oct 30, 2001 3:09 pm

help with sock connections

2001-10-30T13:06:00-04:00

Code:

while {$text != ""} {  set $text [read $sock]  msn:putchan "user" "$text"}

But the eggdrop is stoned when there is a connection

Statistics: Posted by Guest — Tue Oct 30, 2001 1:06 pm

help with sock connections

2001-10-30T12:18:00-04:00

how can I make a while with read?

Code:

[13:48] TCL error [test]: bad argument "text": should be "nonewline"

someting is wrong

Statistics: Posted by Guest — Tue Oct 30, 2001 12:18 pm

help with sock connections

2001-10-30T11:41:00-04:00

use the "read" command for this, you can pass it a length (in bytes) of how many chars you want to read.

Thus, if the command header tell you the message is 130 chars long, then you use the read command to read 130 bytes

Statistics: Posted by ppslim — Tue Oct 30, 2001 11:41 am

help with sock connections

2001-10-30T11:31:00-04:00

Thanks, But now my problem isn't gone
the tcl sockets don't read msg from server whitout the crlf
same problem as the eggdrop connect :'(

[ This Message was edited by: Martin2k on 2001-10-30 08:34 ]

Statistics: Posted by Guest — Tue Oct 30, 2001 11:31 am

help with sock connections

2001-10-30T01:13:00-04:00

Using gets isn't going to get you any farther than eggdrop sockets, because gets looks for a cr or lf. Read the msn protocol... there is a field that tells the length of the message. So, you need to parse the server message correctly, extract the length, then use the 'read' command, which lets you read an arbitrary number of bytes or characters (depending on the channel encoding).

Also, for the example you have, you shouldn't use the -async flag, because that creates an async socket, which means the socket is created, but not connected. You can't read any data from it until it is connected.

Ok, I just telnetted to the address you posted, and here is another problem with you sample code: the msn server doesn't send you anything until you've sent it something. If you send it the wrong thing, it just disconnects you.

Try this:

Code:

set sock [socket messenger.hotmail.com 1863]puts $sock "USR 1 MD5 I you@hotmail.com"puts $sock "USR 1 MD5 S blah"flush $sockwhile {[gets $sock text] != -1} {  putlog "Server: $text"}putlog "Server closed connection"

Statistics: Posted by stdragon — Tue Oct 30, 2001 1:13 am

help with sock connections

2001-10-29T22:00:00-04:00

It is likely that there is no data to read right after making the connection attempt.

It is best to use the "fileevent" command to setup a script to read the details, when somthing is received.

The "eof" command returns 1 or 0 - so eof will never equal "".

the if statment should be somthing like

if {![eof $idx]} {

Statistics: Posted by ppslim — Mon Oct 29, 2001 10:00 pm

help with sock connections

2001-10-29T21:37:00-04:00

Code:

set idx [socket -async messenger.hotmail.com 1863]while {[eof $idx] != ""} {set data [gets $idx]putlog "msn: $data"}}

is that the best way to do that?
or not? (I don't know if it works )

Statistics: Posted by Guest — Mon Oct 29, 2001 9:37 pm

help with sock connections

2001-10-29T21:18:00-04:00

Eggdrops scripted sockets, or TCL sockets are the only way.

Eggdrop sockets have proven to be incompatible with this system, and TCL sockets are not giving you any luck.

The only other option, is to use a help application.

Where your TCL script calls a third-party program using the "exec" command, and the the returned value is used for message grabbing.

Statistics: Posted by ppslim — Mon Oct 29, 2001 9:18 pm

help with sock connections

2001-10-29T21:06:00-04:00

but when there is no connection he give's a tcl error
[23:04] TCL error [test]: can not find channel named "sock1688"

I can't use that in my script I think, is there no better way?

Statistics: Posted by Guest — Mon Oct 29, 2001 9:06 pm

help with sock connections

2001-10-29T20:04:00-04:00

The 'eof' command lets you know when the socket is closed.

Browse through the tcl commands like ppslim said, it tells you all the stuff you need to know

Statistics: Posted by stdragon — Mon Oct 29, 2001 8:04 pm

help with sock connections

2001-10-29T13:36:00-04:00

A thanks, But how can I check of sock is open or close?

Statistics: Posted by Guest — Mon Oct 29, 2001 1:36 pm