View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000192 | LDMud | Other | public | 2004-11-26 22:31 | 2004-11-26 22:31 |
| Reporter | Assigned To | ||||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | new | Resolution | open | ||
| Summary | 0000192: Socket specification (e.g. on the command line) | ||||
| Description | Short: Idea for socket specification From: Lars Duning <lduning@peopledoc.com> Date: Mon, 25 Jan 1999 13:00:04 +0000 Type: Feature State: Unclassified All types of servers need a socket address. This socket address can have different formats. a.UNIX-sockets The format for a UNIX-socket is 'unix:<socket path>' or 'local:<socket path>'. The path can be an absolute path beginning with a '/' or a relative path to 'tnt_dir'. Example: unix:/tcp/sockets/convers b.INET-sockets The format for a INET-socket is 'ip-address:port'. ip-address can be a hostname, an ip-address or a '*' for any ip-address. Port can be any valid port number or a name for a service. Example: *:3600 199.199.10.10:ftp foo.bar.com:2000 | ||||
| Tags | No tags attached. | ||||
| External Data (URL) | |||||
