From WikiChip
Difference between revisions of "mirc/commands/sockmark"
m (Bot: Automated text replacement (-<small>Note: Individual switches were not taken into consideration.</small> +)) |
m (Bot: Automated text replacement (-Added On:.+\n?\n?\n?\n?\n? +)) |
||
Line 37: | Line 37: | ||
== Compatibility == | == Compatibility == | ||
Added: mIRC v5.3 | Added: mIRC v5.3 | ||
− | |||
− | |||
− | |||
− | |||
== See also == | == See also == |
Revision as of 23:31, 5 July 2014
The /sockmark command assigns temporary data to a socket to be referenced later using $sock(<name>).mark. Leaving the [temp data] parameter $null will clear the socket mark. The sockmark command can be used to assign the same data to multiple sockets using a <wild_name> wildcard pattern.
Limitations
The [temp data] is limited to (4,141 - [length of <sock_name>]) characters. I.e. with a socket named "x", you can store up to 4140 characters.
Synopsis
/sockmark <name> [temp data] /sockmark <wild_name> [temp data]
Switches
None
Parameters
- <name> - The handle name of the socket
- <wild_name> - A wildcard pattern to match
- [temp data] - The temporary socket's data
Example
The example below is a demonstration of how you would use it. It does not actually function.
; Non-functioning example, shows practical usage only on $*:text:/^!foo (\S+)$/Si:#:{ ; if ( .. validate input .. ) { sockopen sock1 www.example.com 80 sockmark sock1 $regml(1) } on *:sockopen:sock1:{ ; submit the information we got from the user sockwrite -nt $sockname GET /foobar.php?q= $+ sock($sockname).mark HTTP/1.0 sockwrite -nt $sockname Host: www.example.com sockwrite -nt $sockname $crlf } ; on *:sockread:sock1: { ; .... ; }
Compatibility
Added: mIRC v5.3
See also
- List of commands
- List of identifiers
- $sock
- $sockname
- $sockerr
- $sockbr
- /sockaccept
- /sockclose
- /socklist
- /socklisten
- /sockopen
- /sockpause
- /sockread
- /sockrename
- /sockudp
- /sockwrite
mIRC commands list