I have make A script thats connecting to the msn server, my script is online but now I need help!
how can I get a msg whitout crlf from the server.
and how can I close a connection?
This is the new home of the egghelp.org community forum.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.
help with sock connections
-
MMartin2k
ehh I don't know but I think the eggdrop connect 
Code: Select all
proc msn:connect { } {
global msn
set msn(idx) [connect $msn(serv) $msn(port)]
control $msn(idx) msn:get
msn:putchan "info" "$msn(idx) connecting to $msn(serv) $msn(port)"
putidx $msn(idx) "VER $msn(num) MSNP5 MSNP4 CVRO"
}
As far as I know, eggdrop strips crlf off the text for you, so you don't have to do anything. The string passed to your control procedure, msn:get, should be fine.
Also, you might want to change putidx to putdcc. Putidx is deprecated and may go away in future eggdrop versions.
To close the connection, use killdcc.
Also, you might want to change putidx to putdcc. Putidx is deprecated and may go away in future eggdrop versions.
To close the connection, use killdcc.
The stuff you're using is eggdrop's dcc support.
Tcl has commands to deal with network connections, too. Look at the 'socket' command; 'fileevent' and 'fconfigure' may be helpful.
But it doesn't sound like you need tcl sockets. Your question 'how can I get a msg whitout crlf from the server' was already answered.. didn't it work? Or maybe you could clarify your question?
Tcl has commands to deal with network connections, too. Look at the 'socket' command; 'fileevent' and 'fconfigure' may be helpful.
But it doesn't sound like you need tcl sockets. Your question 'how can I get a msg whitout crlf from the server' was already answered.. didn't it work? Or maybe you could clarify your question?
-
MMartin2k
Eggdrop doesn't need crlf... as long as there is either a cr or an lf, it will work. If your network doesn't send cr OR lf, then you shouldn't be using eggdrop sockets, use tcl's builtin ones instead. Even then it will be trickier than normal.
If it does send at least cr or lf, then something else in your script must be messed up.
If it does send at least cr or lf, then something else in your script must be messed up.
OK, after doing some basic research on the MSN protocol, I have discovered the following.
Each full command, including it's arguments is termanated with a CRLF.
When using eggdrop's "connect" tcl command, you need to put the connection under control of a script. Once this is done, the script is free to do what it wishes with the connection.
The script that is called when data is available, is passed the IDX of the connection and the data sent. The script is called once, each time it meats a CRLF.
The data the script recieves is CRLF sriped, so there is no need to get any such message, as this has allready been done for you.
To kill a connection, you use the "killdcc" command. You pass it the IDX of the connection.
For more info on the MSN protocol (and the basis of my reasearch) view This page (Section 5.2 for command syntax)
Each full command, including it's arguments is termanated with a CRLF.
When using eggdrop's "connect" tcl command, you need to put the connection under control of a script. Once this is done, the script is free to do what it wishes with the connection.
The script that is called when data is available, is passed the IDX of the connection and the data sent. The script is called once, each time it meats a CRLF.
The data the script recieves is CRLF sriped, so there is no need to get any such message, as this has allready been done for you.
To kill a connection, you use the "killdcc" command. You pass it the IDX of the connection.
For more info on the MSN protocol (and the basis of my reasearch) view This page (Section 5.2 for command syntax)
-
MMartin2k
the server say:
on the last line there is no crlf 
Code: Select all
MSG martinkollaard@hotmail.com Martin 131
Content-Type: text/plain; charset=UTF-8
X-MMS-IM-Format: FN=MS%20Shell%20Dlg; EF=; CO=0; CS=0; PF=0
hello (no crlf)
To get this message you would have to convert all your scripts over to TCL sockets, as Eggdrops connect and script based socket handling is not adiquate for this purpose.
According to section 8.8 of the RFC, the arguments passed with the command include the length (in bytes) of the message, including it's header.
From this, we can deduct, that the example you gave was an incorectly formatted header, most likely made op, as the details do no match.
Only TCL sockets will provide the ability to read from a socket before receiving the CRLF.
Eggdrop's connect and script controled sockets, do not provide the ability to read the data before a CRLF is received, thus the message isn;t received correctly.
According to section 8.8 of the RFC, the arguments passed with the command include the length (in bytes) of the message, including it's header.
From this, we can deduct, that the example you gave was an incorectly formatted header, most likely made op, as the details do no match.
Only TCL sockets will provide the ability to read from a socket before receiving the CRLF.
Eggdrop's connect and script controled sockets, do not provide the ability to read the data before a CRLF is received, thus the message isn;t received correctly.
-
MMartin2k
TO teach you would be long winded.
Try reading up on the fconfigure, fblocking, read, gets, puts, socket and fileevent in the TCL man pages.
The TCL man pages are available here for TCL 8.0.5 Here for 8.3
Try reading up on the fconfigure, fblocking, read, gets, puts, socket and fileevent in the TCL man pages.
The TCL man pages are available here for TCL 8.0.5 Here for 8.3