irc-bot/client.mli

type t

val write : t -> Command.t -> unit
val handle_connection : Unixqueue.event_system -> Unixqueue.group -> Unix.file_descr -> unit
More modules, now parsing commands This is where I realized that there's no point in passing around a "server" object, since it's entirely reasonable to expect one server per running instance. 2008-02-28 22:00:24 -07:00			`type t`
Move away from OO, IRC command parser + working test 2008-02-27 22:50:27 -07:00
More modules, now parsing commands This is where I realized that there's no point in passing around a "server" object, since it's entirely reasonable to expect one server per running instance. 2008-02-28 22:00:24 -07:00			`val write : t -> Command.t -> unit`
Properly closing client connections, reworked client connection creation Now the test script has two subsequent connections in it, for great justice. 2008-03-06 21:30:49 -07:00			`val handle_connection : Unixqueue.event_system -> Unixqueue.group -> Unix.file_descr -> unit`
Move away from OO, IRC command parser + working test 2008-02-27 22:50:27 -07:00