…s in their app and after I brief convo I assumed they were right. After stepping through the problem with them confirmed this wasn't the case. Still doesn't mean I don't need to improve things though :)
|Failed to load latest commit information.|
|lib/em||Fixing a small bug in a pretty hackish way. Will clean up a bit more …|
|README||I take back the last commit. Someone was blaming this lib for problem…|
|em-syslog.gemspec||Fixing a small bug in a pretty hackish way. Will clean up a bit more …|
|test.rb||Fixing a small bug in a pretty hackish way. Will clean up a bit more …|
em-syslog ######### Simple syslog integration into EventMachine at the class level. Still needs work and testing. To install: git clone git://github.com/melito/em-syslog.git -or- sudo gem install melito-em-syslog -s http://gems.github.com SYNOPSIS: require 'em/syslog' # Setup syslog EM.syslog_setup('centralserver.com', 514) # Send commands EM.emergency('system is unusable') EM.alert('action must be taken immediately') EM.critical('critical conditions') EM.error('error conditions') EM.warning('warning conditions') EM.notice('normal but significant conditions') EM.informational('informational messages') EM.info('informational messages (short name for the previous)') EM.debug('debug-level messages') BUGS: kqueue doesn't seem to work. (Haven't tested epoll) TODO: Benchmark Take some of the server examples and insert. Make sure blocking is minimal/non-existant Add support for syslog-ng Refactor Add support for TCP (syslog-ng) Add support for TLS (syslog-ng) Clean up API Just improve everything. FIXES: Was creating a new datagram socket everytime a packet was sent out. Only use one now.