OSSP CVS Repository

ossp - History for /ossp-pkg/l2/l2_ch_irc.c
Not logged in
[Honeypot]  [Browse]  [Home]  [Login]  [Reports
[Search]  [Ticket]  [Timeline
  [Directory]  [Show Milestones

DateVersion Description
2005-Oct-03 10:08    1.10    Check-in [5217]: Adjust copyright messages for new year 2005. By rse. (diff)
2005-Jan-24 16:03    1.9    Check-in [4979]: Adjust copyright messages for new year 2005. By rse. (diff)
2003-Jan-06 12:41    1.8    Check-in [3065]: - remove trailing whitespaces - adjust copyright messages - consistently use "OSSP l2" - consistently talk about "Flexible Logging" - use standard OSSP ASCII-art By rse. (diff)
2002-Jul-30 21:08    1.7    Check-in [2437]: polish for release By rse. (diff)
2002-Jul-25 15:33    1.6    Check-in [2354]: proposal to use getservbyname() or successor By thl. (diff)
2002-Jan-02 18:07    1.5    Check-in [1492]: bump copyright year By rse. (diff)
2001-Nov-07 14:05    1.4    Check-in [1260]: Hell, I've seldom seen that it is needed to prepare and adjust such a lot of subtle details of existing code in order to make a new feature implementable in a straight-forward way. Anyway, here comes one more preparation change for the forthcoming channel tree specification parser:

- change l2_util_setparam() to take an l2_env_t parameter which allows the function to report better error messages.

- completely rewrite l2_util_setparam() to support calls l2_channel_configure(ch, "n1=v1,n2=v2,n3=v3") and/or l2_channel_configure(ch, "n1=%x,n2=%x,n3=%x", v1, v2, v3) instead of l2_channel_configure(ch, "n1,n2,n3", v1, v2, v3)

  This is both a step forward to make the interface of
  l2_channel_configure() more flexible (because one now can directly
  inline values instead of having them to be passed explicitly) and
  allows the spec parser not having to know the type (integer, floating
  point or string) of a parameter (which is important if one wants the
  parser to be independent of the implementing channel handlers).
 By rse. (diff)
2001-Nov-07 12:37    1.3    Check-in [1259]: More preparations for forthcoming channel tree specification parser (especially to allow the parser to determine the handler structure from a handler name without introducing another and this way redundant sub-API):

- add "char *name" to l2_handler_t in order to tag each handler structure with the corresponding channel name

- add l2_env_handler() function to add handler to l2_env_t objects. All l2_handler_xxxx are automatically pre-configured there after l2_env_create().

- change l2_channel_create() to take a "const char *name" (handler name) instead of the "l2_handler_t *h" (handler pointer) to make the stuff consistent and more clear.

- adjust l2_test.c to reflect the changes. By rse. (diff)

2001-Oct-19 15:06    1.2    Check-in [1197]: First cut for an IRC output channel. This beast is able to send the message to the IRC channel, but the whole client/server communication is not quite correct because I don't know how to correctly deal with the server responses due to the fact that the IRC protocol (according to the RFC) is asynchronous and there can be replies but there have no to be replies. The effect is that currently we see:

| *** l2_test (~rse@dev10.dev.de.cw.net) has joined channel #l2 | <l2_test> A program of user rse on host dev10.dev.de.cw.net logged at Fri, 19 | Oct 2001 15:01:27 CEST: | <l2_test> 0Checking localhost foo [12345/myparm] | <foo\x01bar><66:6f:6f:01:62:61:72><Zm9vAWJhcg==> | *** Signoff: l2_test (EOF From client)

As you can see, the "EOF from client" is the problem. Currently it is caused by a sa_shutdown(), but I don't know how to program it. So, feel free to jump in and fix the communication of this channel. By rse. (diff)

2001-Oct-04 16:58    1.1    Check-in [1071]: Birth of IRC channel. By ms.

CVSTrac 2.0.1