From c8b2ef7b899766d04562f7e04a84251cea8fa701 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 6 Apr 2013 13:14:44 +0200 Subject: tagging ychat-0.8.0 --- CHANGES | 168 ++- COPYING | 0 Makefile | 89 +- NEWS | 14 + README | 670 +++++++-- RELEASES | 57 +- TODO | 79 +- configure | 1618 +--------------------- etc/ychat.conf | 55 +- html/favicon.ico | Bin html/frameset.html | 12 +- html/index.html | 46 +- html/input.html | 52 +- html/notfound.html | 4 +- html/online.html | 21 +- html/stream.html | 42 +- html/style.css | 45 +- scripts/astyle.sh | 3 +- scripts/makeyhttpd.pl | 87 +- scripts/version.sh | 9 +- src/Makefile.in | 34 +- src/chat/base.h | 154 ++- src/chat/base.tmpl | 49 +- src/chat/chat.cpp | 482 ++++--- src/chat/chat.h | 71 +- src/chat/gcol.cpp | 161 ++- src/chat/gcol.h | 29 +- src/chat/perm.cpp | 69 +- src/chat/perm.h | 44 +- src/chat/room.cpp | 100 +- src/chat/room.h | 95 +- src/chat/sess.cpp | 25 +- src/chat/sess.h | 22 +- src/chat/sman.cpp | 126 +- src/chat/sman.h | 28 +- src/chat/user.cpp | 691 +++++----- src/chat/user.h | 241 ++-- src/cli/cli.cpp | 486 ++++--- src/cli/cli.h | 28 +- src/conf/conf.cpp | 218 +-- src/conf/conf.h | 15 +- src/configure | 1884 +++++-------------------- src/contrib/crypt/md5.cpp | 333 ++--- src/contrib/crypt/md5.h | 15 +- src/contrib/crypt/md5crypt.cpp | 233 ++-- src/contrib/xml/tinyxml.cpp | 1679 +++++++++++----------- src/contrib/xml/tinyxml.h | 2242 +++++++++++++++++------------- src/contrib/xml/tinyxmlerror.cpp | 44 +- src/contrib/xml/tinyxmlparser.cpp | 2684 ++++++++++++++++++------------------ src/data/con.cpp | 26 +- src/data/con.h | 12 +- src/data/con_base.h | 10 +- src/data/data.cpp | 133 +- src/data/data.h | 26 +- src/data/data_base.cpp | 116 +- src/data/data_base.h | 42 +- src/glob.h | 232 +++- src/html.cpp | 132 +- src/html.h | 36 +- src/incl.h | 19 +- src/logd.cpp | 181 +-- src/logd.h | 36 +- src/main.cpp | 126 +- src/maps/hashmap.h | 51 +- src/maps/hashmap.tmpl | 124 +- src/maps/mtools.h | 2 +- src/maps/mtools.tmpl | 5 +- src/maps/nhashmap.h | 12 +- src/maps/nhashmap.tmpl | 12 +- src/maps/shashmap.h | 53 +- src/maps/shashmap.tmpl | 142 +- src/memb/memb.h | 50 +- src/memb/memb.tmpl | 67 +- src/memb/tupel.h | 2 + src/memb/tupel.tmpl | 14 +- src/modl.cpp | 160 ++- src/modl.h | 32 +- src/mods/commands/Makefile.in | 2 +- src/mods/commands/yc_about.cpp | 74 +- src/mods/commands/yc_all.cpp | 77 +- src/mods/commands/yc_away.cpp | 126 +- src/mods/commands/yc_col.cpp | 127 +- src/mods/commands/yc_compopt.cpp | 21 +- src/mods/commands/yc_exec.cpp | 84 +- src/mods/commands/yc_fake.cpp | 43 +- src/mods/commands/yc_getroom.cpp | 70 +- src/mods/commands/yc_getrusage.cpp | 69 +- src/mods/commands/yc_help.cpp | 81 +- src/mods/commands/yc_invisible.cpp | 45 +- src/mods/commands/yc_j.cpp | 183 ++- src/mods/commands/yc_ko.cpp | 88 +- src/mods/commands/yc_m.cpp | 65 +- src/mods/commands/yc_md5.cpp | 84 +- src/mods/commands/yc_me.cpp | 67 +- src/mods/commands/yc_morph.cpp | 77 +- src/mods/commands/yc_msg.cpp | 94 +- src/mods/commands/yc_q.cpp | 27 +- src/mods/commands/yc_reload.cpp | 29 +- src/mods/commands/yc_ren.cpp | 110 +- src/mods/commands/yc_s.cpp | 81 +- src/mods/commands/yc_set.cpp | 175 ++- src/mods/commands/yc_template.cpp | 25 +- src/mods/commands/yc_time.cpp | 27 +- src/mods/commands/yc_topic.cpp | 138 +- src/mods/commands/yc_uptime.cpp | 27 +- src/mods/commands/yc_users.cpp | 31 +- src/mods/commands/yc_version.cpp | 21 +- src/mods/html/Makefile.in | 4 +- src/mods/html/yc_admin.cpp | 117 +- src/mods/html/yc_colors.cpp | 52 +- src/mods/html/yc_help.cpp | 76 +- src/mods/html/yc_loggedin.cpp | 31 +- src/mods/html/yc_options.cpp | 81 +- src/mods/html/yc_register.cpp | 165 +-- src/monitor/dump.cpp | 27 +- src/monitor/dump.h | 31 +- src/msgs.h | 163 ++- src/name.cpp | 34 +- src/name.h | 20 +- src/ncur/menu.cpp | 148 +- src/ncur/menu.h | 28 +- src/ncur/ncur.cpp | 368 ++--- src/ncur/ncur.h | 53 +- src/reqp.cpp | 487 +++---- src/reqp.h | 49 +- src/sign.cpp | 5 +- src/sign.h | 3 +- src/sock/sock.cpp | 594 +++++--- src/sock/sock.h | 96 +- src/sock/sslsock.cpp | 34 +- src/sock/sslsock.h | 32 +- src/thrd/pool.cpp | 271 ++-- src/thrd/pool.h | 68 +- src/thrd/thro.cpp | 23 +- src/thrd/thro.h | 24 +- src/time/timo.cpp | 20 +- src/time/timo.h | 12 +- src/time/timr.cpp | 165 +-- src/time/timr.h | 81 +- src/tool/dir.cpp | 44 +- src/tool/dir.h | 24 +- src/tool/tool.cpp | 256 ++-- src/tool/tool.h | 28 +- src/wrap.cpp | 139 +- src/wrap.h | 127 +- 145 files changed, 11430 insertions(+), 11924 deletions(-) mode change 100644 => 100755 COPYING mode change 100644 => 100755 html/favicon.ico mode change 100644 => 100755 html/style.css diff --git a/CHANGES b/CHANGES index 9994891..ffb446d 100644 --- a/CHANGES +++ b/CHANGES @@ -1,20 +1,150 @@ -Changes from 0.5.4-STABLERELEASE to 0.5.5-STABLERELEASE -- Added scripts/version.sh (can be invoked by gmake version) -- Fixed a bug in the session manager. -- Removed the large animated GIF graphic. - -Changes from 0.5.3-LEGACYRELEASE to 0.5.4-STABLERELEASE -- Backported reqp::get_url from yChat 0.7.8-CURRENT. -- Tagged 0.5-STABLE - -Changes from 0.5.2-LEGACYRELEASE to 0.5.3-LEGACYRLEASE -- Code cleanup -- Added ./scripts/* -- Added gmake stats option - -Changes from 0.5.1-RELEASE to 0.5.2-LEGACYRLEASE -- Changed this branch into a LEGACY branch. -- Rewrote the dynamic thread pool (backport from 0.7.8-CURRENT). -- Added scripts/* -- Code now uses ANSI C++ style with 2 space code indenting. +-Changes from 0.7.9.2-RELEASE to 0.8-RELEASE +$ Modified the Makefiles, so that they produce valid output while using +$ the -j flag of gmake. +$ OpenSSL support has been integrated. Thanks to CryptoMail.org for patching! +$ The next release will also have a credits section in the README! +$ The HTTP parsing stuff has been reviewed and improved by CryptoMail as well. +$ Also a mini bug of the configure script has been fixed. +-Changes from 0.7.9.1-RELEASE to 0.7.9.2-RELEASE - +$ Added monitor/dump, and the dump command to the CLI. +$ Fixed a bug in the session manager. +$ Added gmake dist do the README. +$ Added the charset to the HTTP-header. + +-Changes from 0.7.9-RELEASE to 0.7.9.1-RELEASE - +$ Fixed etc/ychat.conf (Its now valid XML) +$ Fixed some typos. +$ Added the scripts/makedist.sh script, which can be invoked by gmake dist. +$ yhttpd.org has been renamed to yChat.org. The yhttpd.org SLD will be +$ canceled! The yhttpd.org Homepage will remain on yChat.org! + +-Changes from 0.7.8-RELEASE to 0.7.9-RELEASE - +$ In the system messages will be the user printed which has requested the + specified module. +$ Removed the cursor from the ncurses interface. +$ Added wrap::init_wrappers -> The main.cpp is now shorter. +$ Added some Makefile modifications +$ Bugfix: cleanipcache shouldn run every minute but every 10! +$ Bugfix: scripts/stats.pl now counts all text-files properly. + +-Changes from 0.7.7.1-RELEASE to 0.7.8-RELEASE - +$ Updated the yhttpd generation script due new sources in src/memb. +$ Changd some hashmaps back into simple std::map objects, this might +$ has resulted in some bugs due slow hashmap initialization time. +$ Hashmaps now only should being used on permanent objects. +$ Rewrote the dynamic thread pool. +$ makeyhttpd now also removes the yChat specific form etc/yhttpd.conf +$ automatically. +$ Implemnted an IP Cache (makes yChat faster). +$ Implemented signal catcher: +$ SIGUSR1 will clear the html template cache. +$ SIGUSR2 will reload the dynamic modules. +$ SIGSEGV can be catched if defined in src/glob.h. +$ SIGHUP, SIGINT and SIGTERM will shutdown yChat cleanly. +$ Added Allow: GET to the HTTP header. +$ Bugfix: The httpd.logging.accesslines now will be read correctly. +$ Bugfix: JavaScript messages now wont be logged. + +-Changes from 0.7.7-RELEASE to 0.7.7.1-RELEASE - +$ Bugfix in main.cpp which resulted in a core dump on yChat startup. + +-Changes from 0.7.6-RELEASE to 0.7.7-RELEASE - +$ Major code cleanup. +$ Bugfix in /col. +$ Bugfix in gcol #1 (destroy session also if no database is used). +$ Bugfix in gcol #2 (now runs each hour not once a day). +$ Renew the style.css and stream.html. + +-Changes from 0.7.5-RELEASE to 0.7.6-RELEASE - +$ Removed the old hash maps and included the SGI C++ STL extenstion +$ hash_map. + +-Changes from 0.7.4.1-RELEASE to 0.7.5-RELEASE - +$ Garbage collector will now run once a hour rather than each ten minutes. +$ Dynamic thread pool improvements. +$ Removed equiv-http-refresh meta tag from the online list. +$ Minor bugfix in the /topic command. +$ Implemented "User list". + +-Changes from 0.7.4-RELEASE to 0.7.4.1-RELEASE - +$ Dynamic thread pool bugfix (dead lock). + +-Changes from 0.7.3-RELEASE to 0.7.4-RELEASE - +$ Code cleanup. +$ Made the thread pool increasing dynamic. +$ Added some thread pool optimazions. +$ Added some more ${MAKE} vars to the Makefiles. +$ Added Content-length to the HTTPD header. +$ Added the !command to the command line interface. +$ Added Content-type text/plain. +$ Added scrolling checkbox to input.html. +$ Removed modl from yhttpd. Dynamic modules are not needed in yhttpd yet. +$ Improved session engine. +$ Fixed auto logout bug. +$ Fixed newline bug (one \n too much for each html template). +$ Logging can now be completely disabled. + +-Changes from 0.7.2 to 0.7.3-RELEASE - +$ Added FreeBSD 5.3-RELEASE support. +$ Added chat.enableguest option. +$ Added the /all command (Global system message). +$ Renamed the /getstatus command into /about. +$ Fixed the &-bug (& should be allowed in messages). \AND is now a +$ synonym for & too. +$ Fixed the /msg bug (In /msg the string replacer should be activated). +$ Fixed logging bug (do not log any timestamps if there are no messages). + +-Changes from 0.7.1 to 0.7.2-RELEASE - +$ New features: +$ /morph. +$ Added the new standard html template design. +$ Bugfixes: +$ /away prints a . instead of a : if no away reason is given. +$ /ko message was wrong. Displayed not room name of the user to be kicked out. +$ /invisible command displayed wrong private messages. +$ /getstatus had no help text. +$ /msg and /s should now print the system time if printalwaystime == true. +$ Added a blank to the /uptime message. +$ /topic now prints the topic in the user's color. +$ Fixed some typos. + +-Changes from 0.7.0 to 0.7.1-RELEASE - +$ Added ${MAKE} to the config file because some Linux distros dont use +$ the "gmake" command for GNU make but just "make"! Modified the +$ configure script to generate a make.version file. +$ Removed some typos from the ychat.conf. +$ Fixed the auto away message. This one will be posted in the room +$ as public rather than only private to the auto-away-user. +$ Fixed some documentation stuff for yhttpd because yhttpd does not +$ need MySQL at all. +$ Added the chat.maxlength.word option. + +-Changes from 0.6 to 0.7.0-RELEASE - +$ Better stability . +$ Better performance (using more hmaps). +$ HTML color switcher menu. +$ New commands: /away /room /j /ren. +$ Simple garbage collector for old user and room objects. +$ Use of the database (MySQL). +$ Nick registration and password protection. +$ Status images for Operator, Half-Operator, Voiced user and Guests. +$ New Makefiles. +$ Useful Perl scripts for sourcecode stats generation etc. +$ Added system_log and room logging to access_log logging. +$ Added time-offset option. +$ Added to the admin interface new options. +$ Added Logout button. +$ Added string replacer there certain substr. of postings will be replaced by another string (such as smiley images). +$ Added Superuser levels and the /ko and /set commands. +$ Added admin CLI (Command Line Interface) mode. +$ Added memory rusage history which tracks memory usage for the last 10 days. +$ Added HTTP POST request parsing. +$ Made yChat more modular so yhttpd can be extracted from it +$ (scripts/makeyhttpd.pl). +$ Added CGI support. +$ Rewrote big parts of the Makefiles and the configure scripts. +$ Made it compatible to GNU G++ 3.4, 3.3, 3.2 and 3.1 (3.0 and earlier do not +$ work). +$ XML based configuration file (ychat.conf). +$ Added default operator option: chat.defaultop. diff --git a/COPYING b/COPYING old mode 100644 new mode 100755 diff --git a/Makefile b/Makefile index a453f44..27a8d90 100755 --- a/Makefile +++ b/Makefile @@ -1,24 +1,95 @@ -MAKE=gmake -all: base - @echo "Now edit the ./conf.txt file and run ./ychat!" +MAKE=`tail -n 1 make.version` +PREFIX=`grep "define PREFIX" src/glob.h | cut -d'"' -f2` +all: version base modules + @echo "Now edit the ychat.conf and run ychat!" + @echo "The config file is searched in the following order:" + @echo " ./ychat.conf " + @echo " ~/.ychat/ychat.conf " + @echo " ./etc/ychat.conf " + @echo " /etc/ychat.conf " + @echo " $(PREFIX)/etc/ychat.conf " + @echo If you want to help the yChat project please run gmake mail + @echo so that the developers receive an email about the platform + @echo being used. + @echo WARNING! This software is EXPERIMENTAL! +mail: + @echo "VERSION:" > mail.tmp + @${MAKE} version >> mail.tmp + @echo >> mail.tmp + @echo "UNAME:" >> mail.tmp + @uname -a >> mail.tmp + @echo >> mail.tmp + @echo "DATE:" >> mail.tmp + @date >> mail.tmp + @echo >> mail.tmp + @echo "COMPILER AND MAKE:" >> mail.tmp + @cat g++.version make.version >> mail.tmp + @cat mail.tmp | mail -s "Successfull build of yChat" successfullbuild@yhttpd.org + @rm -f mail.tmp install: deinstall uninstall: deinstall deinstall: @echo Install/deinstall is not supported! - @echo Start yChat with ./ychat instead! + @echo Start yChat with ./bin/ychat instead! @exit 1 +modules: + @if test -d ./src/mods; then ${MAKE} -C ./src/mods; fi +clean_modules: + @if test -d ./src/mods; then ${MAKE} -C ./src/mods clean; fi base: + @if test -f bin/ychat; then echo "Backing up old binary";if test -f bin/ychat.old; then rm -f bin/ychat.old; fi; mv bin/ychat bin/ychat.old; fi + @perl ./scripts/buildnr.pl + @perl ./scripts/setglobvals.pl @${MAKE} -C ./src clean_base: @${MAKE} -C ./src clean stats: @perl scripts/stats.pl run: - ./ychat + ./bin/ychat +base_start: base + ./bin/ychat gpl: @more COPYING -clean: clean_base -debug: - @gdb ./ychat ychat.core +#//<<* +yhttpdbase: + @perl scripts/makeyhttpd.pl || echo "You need to have perl to do this!" + @echo yhttpd code base has been generated in ../yhttpd +#//*>> +clean: clean_base clean_modules +help: + @echo "You may run ${MAKE} with the following parameters:" + @grep "^ ${MAKE} " README + @echo "For more questions read the README file or contact mail@ychat.org!" +setup: + @./configure + @${MAKE} +config: + @sh -c "scripts/config.sh" + @echo If you run ${MAKE} config from the command line then you may need + @echo to rerun ./configure and recompile all now! + +mrproper: clean + @if test -f src/glob.h.org; then mv -f src/glob.h.org src/glob.h;fi + @if test -f g++.version; then rm -f g++.version; fi + @if test -f make.version; then rm -f make.version; fi + @if test -f src/Makefile; then rm -f src/Makefile; fi + @if test -f bin/ychat; then find bin/ -name "*ychat*" | xargs rm -f; fi + @if test -d src/mods; then find src/mods/*/ -name Makefile | xargs rm -f; fi + @find . -name "*.add" | xargs rm -f + @ls | grep core | xargs rm -f version: - @sh ./scripts/version.sh + @./scripts/version.sh +debug: + @gdb bin/ychat ychat.core +confdebug: + ./configure -g3 -ggdb +dist: + @./scripts/makedist.sh +ssltest: + openssl genrsa -des3 -out privkey.pem 2048 + openssl req -new -x509 -key privkey.pem -out cert.pem -days 1095 + @mv -f privkey.pem cert.pem etc + + + diff --git a/NEWS b/NEWS index 576279d..57ca75f 100644 --- a/NEWS +++ b/NEWS @@ -1,3 +1,17 @@ +::(25.05.05)::yChat 0.8-RELEASE is available. This is the first release of the 0.8-CURRENT branch. OpenSSL support has been integrated. Thanks to CryptoMail.org for the patches! Also, the HTTP parsing methods have been reviewed and improved by the CryptoMail crew as well. In addition, several smaller bugs were fixed. +::(08.05.05)::yChat 0.7.9.3-RELEASE is available. This is the first STABLE release of the 0.7 branch. yChat 0.7.9.2 still has been of CURRENT. The new release only includes some bugfixes related to the Makefiles, configure-scripts. Also a security patch for the 0.8-CURRENT branch has been backported into 0.7.9.3. +::(04.05.05)::OpenSSL support has been integrated into yChat 0.8-CURRENT. The 0.8-RELEASE will come soon after some additional documentation stuff related to OpenSSL has been done. Thanks to CryptoMail.org for mailing the OpenSSL patch. +::(13.04.05)::The 0.7 yChat branch now became stable. At this point, its yChat 0.7.9.3-STABLE, which will become some day the first STABLERELEASE of the 0.7 branch. +::(12.04.05)::Released yChat 0.5.5 of the STABLE branch. This release includes a security fix in the session manager. We also put the yChat 0.8 branch into CVS. The 0.7 branch will become stable soon. +::(10.04.05)::Released yChat 0.7.9.2. This release adds the dump command for the command line interface which prints out the internal yChat data structure. This feature makes it easier to track bugs. Also, a big bug of the session manager has been wiped out. +::(08.04.05)::C++ yChat is now about 2 years old. Happy birthday yChat! The next few releases of the CURRENT branch will mostly contain bugfixes and stability improvements. We want to get ready to change 0.7-CURRENT into 0.7-STABLE in order to work on newer 0.8-CURRENT versions. +::(07.04.05)::Released yChat 0.7.9.1. This release includes some minor bugfixes. The ychat.conf file is now valid XML. Also some typos have been fixed. Also a scripts/makedist.sh script has been added which creates a .tar.bz2 ball of the current source tree. +::(10.03.05)::Released yChat 0.7.9. The logging capability has been improved. All chat command requests will be logged. The ncurses interface has been improved. Some code has been cleaned up. +::(07.03.05)::Released yChat 0.5.4. This is a STABLERELEASE. The HTTP parsing methods have been backported from yChat 0.7.8. Also some minor bugfixes were made.This is the first STABLERELEASE of yChat ever. +::(05.03.05)::Released yChat 0.7.8. This release includes an IP cache for more speed. An UNIX signal catcher class has been added. SIGUSR1 and SIGUSR2 now clean the template cache or reload all dynamic modules. Added "Allow" to the HTTPD header. Also, lots of Bugfixes and minor improvements were made. Changed the 0.5 branch into STABLE. The 0.5.4-STABLERELEASE will follow next week. The ychat-stable CVS branch has been opened, which now points to ychat-0.5. +::(02.03.05)::Released yChat 0.5.3. This is a LEGACYRELEASE. It includes a stats generation script located in the scripts/ directory which can be called by gmake stats. Also all the sources have been moved to ./src. Some minor bugfixes are included also. +::(27.02.05)::Released yChat 0.5.2. This is a LEGACYRELEASE. That means, that this version is not official supported. The 0.5.2 version might be interesting by developers who want to have a clean base structure of an existing C++ based chat system. The 0.5.2 version does not have any features besides logging in and single room chatting. Multi rooms can be added easily. +::(24.02.05)::Released yChat 0.7.7.1. This release only includes a yChat startup bugfix. ::(17.02.05)::Released yChat 0.7.6. This release now uses the hash_map class from the SGI STL extension which is more stable then the old Hash Map used by yChat. ::(14.02.05)::Released yChat 0.7.5. The garbage collector will now run once a hour. The dynamic thread pool has been improved. Removed thre equiv-http-refresh meta tag from the online list. Added a minor bugfix in the /topic command. Implemented an HTML based list of all logged in users and the /users command which does the same. ::(13.02.05)::Released yChat 0.7.4.1 This new version includes a major bugfix made in the new dynamic thread pool which has been introdouced in 0.7.4. The bug resulted in a thread pool dead lock.. Tagged yChat 0.7.5-CURRENT into CVS. diff --git a/README b/README index 240c854..536c6e2 100755 --- a/README +++ b/README @@ -1,7 +1,8 @@ -yChat++ Basic; Homepage: www.yChat.org; Version 0.5 +yChat; Homepage: www.yChat.org; Version 0.8-RELEASE + Copyright (C) 2003 Paul C. Buetow, Volker Richter +Copyright (C) 2004, 2005 Paul C. Buetow ----------------------------------------------------------------- - This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 @@ -15,204 +16,571 @@ GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. - ----------------------------------------------------------------- -0.0.0 YCHAT++ BASIC TABLE OF CONTENTS -1.0.0 REQUIREMENTS -1.1.0 TESTED PLATFORMS -1.2.0 IMPORTANT NOTES -1.3.0 HOW TO OBTAIN YCHAT++ -1.3.1 INSTALLATION -1.5.0 CUSTOMIZATION -1.6.0 FILES -1.8.0 CONTACT +YCHAT TABLE OF CONTENTS: + +1.0.0 GENERAL +1.1.0 ABOUT RELEASES +1.2.0 YCHAT FEATURES //<< +2.0.0 INSTALLATION AND SETUP +2.1.0 REQUIREMENTS +2.2.0 TESTED PLATFORMS +2.3.0 HOW TO OBTAIN YCHAT +2.4.0 INSTALLATION QUICK-START +2.4.1 INSTALLATION +2.3.3 HOW TO USE OPENSSL WITH YCHAT +2.3.4 HOW TO USE MYSQL WITH YCHAT //<< +2.3.5 HOW TO USE SCREEN WITH YCHAT +2.3.6 HOW TO USE SIGNALS WITH YCHAT +2.4.0 CONFIGURING YCHAT +2.5.0 YHTTPD CODE BASE GENERATION //<< +3.0.0 EXTENDING YCHAT +3.1.0 SOURCE FILES +4.0.0 DIVERSE +4.1.0 WRITING BUG REPORTS +4.2.0 CONTACT ADDRESSES +4.3.0 CREDITS + +1.0.0 GENERAL + +1.1.0 ABOUT RELEASES + +There are several projects involved: + +- The chat - +Its a HTTP based chat server written in C++. Clients are normal web browsers +such as MSIE or Gecko based browsers using only CSS, HTML and JavaScript. + +- The httpd - +Its a small http server based on the chat's socket and threading engine. +yhttpd does not have as much features but is easy to use and faster than +apache. yhttpd is a subset of the chat. It can be generated using the +srcipts/yhttpdbase.pl script in the chat's source tree. + +- The ycurses - +ycurses is a easy to use and small C++ wrapper of the C ncurses API. + +There are different branches: + +- CURRENT - +The CURRENT branch is unstable, this is the bleeding developing edge with +all the new experimental features. + +A RELEASE of CURRENT can be referred as CURRENTRELEASE. + +- STABLE - +The STABLE branch is more stable than CURRENT. This branch may get new +features as well. But those will be more conservative compared to +CURRENT. + +A RELEASE of STABLE can be referred as STABLERELEASE. + +- LEGACY - +The LEGACY branch has no real support. This branch may get bugfixes and +updates and might get minor improvements. But there is no garuantee to +be bug free and stable at all. LEGACY versions are of historic meaning. + +- DEVEL - +DEVEL is only a meta name. If a version is labeled with DEVEL, then its +currently undefined if this is a CURRENT, STABLE or LEGACY branch. It +can be everything. Commonly DEVEL versions are CURRENT. + +There are also releases made: + +- RELEASE - +There can be RELEASEs made out of each branch. While a branch can get +new features, a RELEASE can not. A RELEASE of a branch is just like +a snapshot. RELEASEs are complete versions to test and use. But keep +in mind, that a RELEASE of the STABLE branch is recommended over a +RELEASE of a CURRENT or a LEGACY branch in a production environment. +RELEASEs of CURRENT are still the bleeding edge and RELEASEs of LEGACY +may be out of date. + +- Short names - + +In addition, each description also has short names: (short names are needed +if your text space is limited which happens very fast in IRC channel topics) + +CURRENT aka CUR aka C +RELEASE aka REL aka R +LEGACY aka LEG aka L +STABLE aka SBL aka S +DEVEL aka DEV aka D +PRE aka P + +STABLERELEASE aka STBREL aka SR +PRERELEASE aka PREREL aka PR +PRELEGACYRELEASE aka PRELEGREL aka PLR +etc... + +The short name of the chat is "yC" +The short name of the httpd is "yh" +The short name of ycurses is "yu" + +//<<* +1.2.0 YCHAT FEATURES + +- Its free & portable - +yChat is developed under the GNU general public license and is based on GNU +tools (gcc, gmake), other open source library stuff (such as libncurses etc.) +and should run on any POSIX capable operating system (such as all Linux based +systems, FreeBSD, NetBSD, OpenBSD and other BSD-Systems and on UNICES like +IRIX, HP-UX, Solaris etc.). + +- There is no need for special chat clients - +yChat is web based, that means clients may only connect to the chat server +with an normal web browser such as Microsoft Internet Explorer or any Gecko- +Engine powerd browsers like Mozilla, Firefox, Camino etc. + +- It has features of a real HTTP webserver - +yChat runs completely stand alone and does not need another webserver to build +on like Apache and does not need to be run via any kind of CGI. yChat creates +its own socket on a customized port (standard port: 2000) and seems to be a full +featured HTTP web server to the clients (web browsers). + +The yChat code base can be converted to an yhttpd code base automaticaly. yhttpd +is the webserver subset of yChat which runs completely stand alone and provides +normal websites to the net. It also supports Common Gateway Interface (CGI) +scripting. + +- Its fast and secure - +yChat is written in C++ which is faster than any Java based Chat-Server or any +server written in a scripting language like PHP, Python or Perl. As the +internal data structures hash maps are used to garuantee searching certain +values in O(1) amount of time. If a hash maps gets full, it will be rehashed. +Currently, yChat has been measured providing over 1000 hits/requests per second +on a FreeBSD based server box while using less than 2% of CPU usage +on a Athlon XP 1900+. Performance seems to be limited by your bandwith only. +Also, each user gets its own session id (random string) with a standard length +of 50 chars to authenticate each logged in user. The length of the session id +can be redefined as well. Also, the session id will get md5-hashed optionally +so thats even harder to reverse engineering the session ids of other users. +Also, yChat supports secure hypertext transfer protocol (HTTPS) connections +using the OpenSSL library. Then, all chat messages will be encrypted in a +secure manner. HTTPS is optional to HTTP (unsecured connections). + +- Its HTML template based and easy to customize via XML based configuration - +All HTML sites are predefined as HTML-Template files and can be easily modified +to use with an customized web design. Also, a lot of yChat preferences can be +set in the main configuration file (ychat.conf). ychat.conf is completely written +in XML 1.0 which makes it easier to use the configuration options in programs of +3rd persons which may want to write some usefull tools for yChat. +yChat caches all HTML and web images to improve overall performance. If needed, the +cache can be cleared to recache new versions of the template files. + +- Its language template based - +The administrator can easily create a new language in which all system messages +appear to the Chat-User. The predefined languages is english but others can be +added easily. The language can be edited in the XML based configuration file. + +- MySQL based database - +Registered users are stored in a MySQL database. C++ Programmers may feel free +to replace the database wrapper class (data.h) with another database routines +to use other databases such as PostgreSQL, SQLite or a text based database etc. +If wished, you can disable database support in the pre-compile options. + +- It has an administration interface - +yChat includes an ncurses based administration interface which tracks some +interesting statistics and system messages and enables you to do certain +administrative tasks. In addition, you can switch to the CLI (command line +interface) mode of the administration interface in order to be provided with +more available functions (like keeping track of the current system usage etc.). +If you dont like ncurses and/or the CLI you can disable both options in the pre- +compile options. + +- It has logging capabilities - +The logging manager keeps track to all yChat system messages (such as users +wich log in and out, modules which are loaded, MySQL queries etc.). Also, an +Apache-Style combined log file format is created by yChat (you can parse this +logfile with any Apache logfile parser like awstats etc.). And last but not +least, all public messages of all available rooms will be logged to disk as +well . To improve performance, you can define the logging puffer (standardly +new logs will be written to disk after each 20 lines). If you want to log +everything immediately, you can reset this option to 1 in ychat.conf. + +- Its modular through own command and dynamic HTML engine - +All chat commands are realized through dynamic loadable module files which can +be recompiled and reloaded without restarting the whole yChat server. Also +HTML-Sites with certain tasks can be compiled as a module like +mods/html/yc_register.so, mods/html/yc_options.so and mods/html/yc_colors.so +etc. so you can also program your dynamic yChat websites in C++. + +- Its multi threaded (POSIX threads) - +There is only one main process which spawns several threads, each for its own +unique task. For example one thread is used to handle the socket manager which +waits for incoming TCP/IP requests, another thread schedules the system timer +which proves if clients are still active or frees not needed memory in certain +time intervals (see also "Garbage collector"). Also, each Chat-User gets it own +thread. There is no need of memory wastage by creating for each task a new +process. All User-Threads are managed by a thread pool to avoid CPU wastage +creating every time a new thread by reusing thread objects which have done its +jobs already and have been readded into the queue of the thread pool. The +standard sizes of the queue and the total pool size can be set in ychat.conf. + +- Its using a smart garbage collection engine - +All users and rooms which dont have to be kept in the main memory (because the +user has logged out or the room has been destroyed because it was empty) will +not be deleted immediately but be placed for about 10 minutes in the yChat +garbage collector. Each time a new room is created the systems checks the +garbage to reuse an inactive room object. If a certain user wants to log in, the +system checks if he is already present in the garbage collector. If yes, he will +be reactivated without wasting expensive database queries to fetch the user's +options. This improves overall performance on heavily loaded yChat servers if a +lot of user and room objects are created and destroyed frequently. +//*>> + +2.0.0 INSTALLATION AND SETUP + +2.1.0 REQUIREMENTS: + +- GNU GCC G++ + The GNU C++ compiler version 3.1 or up. + +- GNU make 3.80 (gmake) or higher + If you dont have a gmake executable but make is gnu make then you need + to add a symlink or alias from gmake to make. + yChat Makefiles only have been tested with GNU make and may not work with + other make versions. + +- SGI STL extension + Includes ext/hash_map which may be already default on every Linux distro. + On *BSD you have to install it first before compiling. On FreeBSD + /usr/ports/devel/stlport is your friend. + +- OpenSSL + Includes libssl and the ssl header files of the open source SSL library. + OpenSSL is only needed if you chose to compile yChat w/OpenSSL support. + +//<<* +- mysql-client 4.x (3.x may do too but is not supported) + Includes libmysqlclient and the mysql.h header files. mysql-client is only + needed if you chose to compile yChat w/database support. + +//*>> +- ncurses 5.x + Includes libncurses and the ncurses.h header files. + +- Screen + Only needed if yChat should run in background with + ncurses or CLI enabled. + +- Perl 5.x + Is needed for some scripts. Is not needed if you use precompiled binaries. + +2.1.0 TESTED PLATFORMS: + +The following platforms have been tested with success. If you find out that +a listed platform did not work at all please contact me: + + Operating system (arch) GNU G++ GNU make +- FreeBSD 5.4-RELEASE (i386) 3.4.2 3.80 +- FreeBSD 5.3-RELEASE (i386) 3.4.2 3.80 + + Tested longer time before: +- FreeBSD 5.2.1-RELEASE (i386) 3.3.3 3.80 +- FreeBSD 4.10-RELEASE (i386) 3.4.1 3.80 +- FreeBSD 4.9-RELEASE (i386) 3.3.4 3.80 +- Gentoo Linux 2004 (i386) 3.3.2 3.80 +- OpenBSD 3.6 SMP (i386) 3.3.2 3.80 +- Red Hat Linux 8.0 SMP (i386) 3.2-7 3.79 +- Slackware Linux 10.0 (i386) 3.4.0 3.80 +- SUSE Linux 9.0 (i386) 3.3.1 3.80 +- SUSE Linux 8.1 (i386) 3.2 3.79.1 + +Other platforms like Linux based systems, other BSD-Systems or UNICES +are very likely to work too. + +2.3.0 HOW TO OBTAIN YCHAT: -1.0.0 REQUIREMENTS: +yChat can be downloaded as a source package or through CVS. -- gcc 3.2 - The GNU C++ compiler. +The packages are located at http://www.yChat.org -> Sourcecode -> +Packages or go to http://pub.buetow.org/yChat/yChat . -1.1.0 TESTED PLATFORMS: +For CVS download type: + +cvs -d:pserver:anonymous@buetow.org:/usr/home/cvs/cvsroot login +( You will be asked for a password. Use "just enter" ). -The following platforms have been tested with success: +vs -z3 -d:pserver:anonymous@buetow.org:/usr/home/cvs/cvsroot co BRANCH +( The sources will be copied into your local folder ) -- Linux with GCC 3.2.0, GNU make 3.79.1 -- FreeBSD 5.1-RELEASE-p2, GCC 3.2.2, GNU make 3.80 ( standard make does not seem work on FreeBSD ). +cvs -d:pserver:anonymous@buetow.org:/usr/home/cvs/cvsroot logout +( Logs your CVS session out ). -1.2.0 IMPORTANT NOTES: +Now you may continue with the installation. -Before you compile the source you have to be sure to use at least GCC -version 3.x with pthreads enabled. ( Type gcc -v to check it ). -GCC 2.95 did not work while testing on linux and WON'T BE SUPPORTED! -If you like to support yChat++, please write us an email and tell what -you can/like/would help ;-]. Please also take a look at the yChat++ -homepage which is located at http://www.yChat.org. +here are different branches in the CVS: + +ychat: This is the latest CURRENT branch of yChat. +ychat-stable: This is the latest STABLE branch of yChat. +ychat-X.Y: This is the branch with the specified version prefix. +yhttpd: This is the latest CURRENT snapshot of yhttpd. + +The CURRENT branch of ychat is mostly untested and unstable, so don't +cry if you get errors. + +2.4.0 INSTALLATION QUICK START + +If you in hury, then you may just type gmake setup. In the yChat configurator +you may just choose all the default values. If done, yChat will get compiled +and is ready to run with ./bin/ychat! If you chose OpenSSL support, then +also run gmake ssltest before starting yChat. + +2.3.1 INSTALLATION + +Invoke "./configure". Afterwards you will get prompted with the before-compile +options of yChat. After choosing those options you are ready to type "gmake" +afterwards. See below what gmake is doing. + +//<<* +If you have choosen MySQL database support, then take a look at section 1.3.2 +how to setup a valid database table. Be also sure to enter the valid MySQL +accessing data in the yChat configuration file which is normally located in +the etc/ychat.conf file if not changed by you with the yChat configurator. +//*>> + +You may also invoke gmake with the following options (the PREFIX can be set +in the yChat configurator which will be launched by the top configure script +or gmake config): + + gmake or gmake all (compiles everything, also modules and runs "gmake mail") + gmake base (only compiles the base) + gmake base_start (only compiles the base and starts the server) + gmake clean (cleans everything) + gmake clean_base (only cleans the base obj and rpo files) + gmake clean_modules (only cleans the modules .so files) + gmake confdebug (runs ./configure with enabling debugging) + gmake config (runs yChat configurator) + gmake debug (runs gdb on ./ychat.core) + gmake dist (creates a .tar.bz2 ball) + gmake gpl (shows the GNU General Public License) + gmake help (shows all available ychat gmake targets) + gmake mail (sends a mail to the yChat developers containing build opts.) + gmake modules (only compiles modules) + gmake mrproper (same as gmake clean plus removing all temp files) + gmake setup (runs all configure scripts and afterwards gmake all) + gmake stats (generates ychat statistics) + gmake ssltest (generates a self signed ssl test certificate) + gmake version (shows the current version of yChat) +//<<* + gmake yhttpdbase (generates an yhttpd code base) +//*>> (See section 1.9 to read about this marks) + +Example: "gmake all install clean" compiles everything, installs it to PREFIX +and cleans the source directories. + +Now its time to run the server with ./bin/ychat. + +Aferwards point your webbrowser to http://yourip:port ! -1.3.0 HOW TO OBTAIN YCHAT++: +... have fun :-). -yChat can be downloaded as a source package or through CVS. +2.3.3 HOW TO USE OPENSSL WITH YCHAT -The packages are located at http://www.yChat.org -> Sourcecode -> -Packages or go to http://programming.buetow.org/CPP-yChat . +If you chose to use OpenSSL support you have to have a valid SSL private and +public key. If you are in hurry, use the gmake ssltest command from the top +source tree directory and follow the instructions. Otherwise type the +following commands manually: -For CVS download type: +The private key can be created w/the following command: -cvs -d:pserver:anonymous@cvs.ychat.berlios.de:/cvsroot/ychat login -( You will be asked for a password. Use "just enter" ). + openssl genrsa -des3 -out privkey.pem 2048 -cvs -z3 -d:pserver:anonymous@cvs.ychat.berlios.de:/cvsroot/ychat co \ - ychat_advanced -( The sources will be copied into your local folder. However, if you - want to obtain the yChat++ Basic sources then replace "ychat_advanced" - "ychat" ). +Afterwards, you can create a self-signed test certificate using the following +command: -cvs -d:pserver:anonymous@cvs.ychat.berlios.de:/cvsroot/ychat logout -( Logs your CVS session out ). + openssl req -new -x509 -key privkey.pem -out cert.pem -days 1095 -Now you may continue with the installation. +Be sure to move the privkey.pem and cert.pem files into the ./etc directory +or edit the path names in the ./etc/ychat.conf file. yChat wont start if there +are no valid files found. -1.3.1 INSTALLATION: +To learn more about SSL certificates, visit http://www.openssl.org/docs/HOWTO/. -Invoke "./configure" and afterwards "make", edit the conf.txt. +Now use https:// and NOT http:// to connect to the yChat server. -Now we want to compile all the dynamic loadable modules of ychat. -Invoke "cd cmnd && ./compile.sh && cd -". All command modules should get -compiled. +//<<* +2.3.4 HOW TO USE MYSQL WITH YCHAT -Now its time to run the server with ./ychat. -Then point your webbrowser to http://yourip:port/index.html ( ignoring -the index.html on the end of the url will not work! ). -... have fun :-). +If you chose to use MySQL database support you have to create a valid database +to use with yChat. -1.5.0 CUSTOMIZATION: +Create a new MySQL database called 'ychat' and type the following command into +a MySQL command line client of your choice: + +USE ychat +CREATE TABLE `user` ( + `uid` int(10) NOT NULL auto_increment, + `nick` varchar(30) NOT NULL default '', + `password` varchar(30) NOT NULL default '', + `color1` varchar(30), + `color2` varchar(30), + `email` varchar(50) default '-', + `registerdate` varchar(30) default '-', + `logincounter` varchar(10) default '0', + `status` char(1) default '3', + PRIMARY KEY (`uid`), + KEY `uid` (`uid`) +) TYPE=MyISAM; +GRANT ALL PRIVILEGES ON ychat.* to ychat@localhost IDENTIFIED BY "yctest"; + +This database uses the default MySQL access informations which are stored in the +ychat.conf file. +//*>> + +2.3.5 HOW TO USE SCREEN WITH YCHAT: + +If you are running yChat in ncurses mode you might want to install +the tool which is called "screen". This will enable you putting the +ncurses interface into the background, closing the terminal session +and reusing the interface later through another terminal. + +Just do: + + screen -S ychat ./bin/ychat ( creates a new session and starts yChat in it ) + ctrl+d+a ( will detach the yChat session ) + ( closing the terminal ) + ( opening a new terminal ) + screen -r ychat ( will return you to the yChat process ) + +Screen will terminate automaticaly if all processes in its sessions are +terminated. + +For a closer look read the screen manual page ( man screen ). + +2.3.6 HOW TO USE SIGNALS WITH YCHAT: + +You can send UNIX signals to yChat. This becomes very interesting if you +don't use the command line interface or the ncurses interface and you +don't have access to the options below. + +Run one of the following commands to send the signal you want: +($PID is here the process id of the current yChat process) + +kill -USR1 $PID # yChat clears the HTML template cache +kill -USR2 $PID # yChat reloads all dynamic loadable modules //<< +kill -HUP $PID # yChat will shutdown savely + +2.4.0 CONFIGURING YCHAT: If you like to customize the design/layout/language of yChat, you will have -to edit msgs.h and glob.h before you compile the sources. Afterwards you can -change the html-template files which are placed in the html/ subdirectory. -Dynamic loadable modules can be found in the cmnd/ subdirectory. +to edit src/msgs.h and src/glob.h before you compile the sources. Afterwards +you can change the html-template files which are placed in the html/ +subdirectory and the language-templates which are placed in the XML config +file (etc/ychat.conf). -1.6.0 FILES: ( This list is not complete ) +Notice, that you dont have to edit the src/glob.h file by hand any more, its +already done by the top ./configure script for you. -conf.txt - The yChat configuration file. ( read by conf.cpp ). +You can edit the etc/ychat.conf to fit your needs. If you dont want to change +the config file, then you also can use ychat start parameters. -base.cpp - Encapsulates vector fields of room's or user ( may be later - hash_maps ) and provides methods for manipulating data - objects. +Exmpl: ./bin/ychat -o chat.database.password secretpassword -hmap.cpp - The hash map implementation which is a very fast data - structure. is needed for saving users, rooms and so on. +You can also use multiple words for a specific option. -main.cpp - This includes the required manager headers for starting - the server and finally regulates the correct starting. +Exmpl: ./bin/ychat -o ychat.version "word1 word2 word3" -modl.cpp - The module loader. Stores pointers of all dynamic loaded - yChat modules in a hash map object and loads new modules - if desired or returns their pointers. +will overwrite the default database password value of the ychat.conf. You can +do this with every configuration element by adding several -o option value +arguments to the start command. -pool.cpp - The implementation of the thread pool. all threads are stored - in a queue. Each thread will be reused if the assigned job is - finished. +Dynamic loadable modules can be found in the mods/ subdirectory. (chat +commands are realized through modules too). Sources of modules can be found +in src/mods instead. If you want to create a new module just create a new +.cpp file and run in src/mods the ./configure script again. Next time +you run gmake your new module gets compiled. -reqp.cpp - This class implements the http request parser. If a client - starts a request to the server the reqp class will be - invoked. +All messages defined in the msgs.h file contain server messages only ( a chat +user never wont read them, only the administrator will get to see them ). -room.cpp - Specifies a chat room. For each chat room an instance of - this class exists. +Read also section 3.0.0 of this README. -thrd.cpp - This class is needed by sock.cpp while creating a POSIX thread. - All data which a thread needs to do its tasks are stored in a - thrd object and then a pointer to it will be passed to the - POSIX thread function. +//<<* +2.5.0 YHTTPD CODE BASE GENERATION -user.cpp - Specifies a chat user. For each chat user an instance of - this class exists. +See docs/yhttpd.txt +//*>> -Abstract classes: +3.0.0 EXTENDING YCHAT -cont.cpp - All classes which need to store "key - value" data sets - inherit from this class. ( cont for content ). +3.1.0 SOURCE FILES -name.cpp - All classes which own a private member string name inherit - from this class. It also provides public get_name and - set_name methods. +This list is not complete. Only the most important files are listed here! -As described ( main.cpp ), there are so called managers. Managers are -accessible through their assigned wrapper classes and may be -instanciated only once. +etc/ychat.conf - The yChat configuration file +html/* - The html template files +src/* - The yChat base sources +src/mods/* - The dynamic loadable modules sources +scripts/* - Some nice scripts needed for building & co. -chat.cpp - The chat manager. Is responsible for managing the internal - data structure of the system and also covers a lot of - important methods of the system. +The following is created by building yChat: +obj/* - The object files of the compiled yChat base +mods/* - The compiled dynamic loadable modules +bin/ychat - The yChat binary (linked by the object files) -conf.cpp - The config manager. Parses the config file specified in - glob.h and stores all the values of it in a map. +Customizable source files (if changed you need to run gmake clean all) +src/glob.h - Contains some global building options +src/msgs.h - Defines some server side messages -html.cpp - The html-template manager. Reads the requested html-template - files, stores them in an internal cache ( averts reading - template-files from hd twice or more ) and parses the - partivular template in order to substituate dynamic values - of it. -mutx.cpp - The mutex manager. Contains all global mutex handlers for - synchronizing POSIX thread shared data. until now only the - stdout is synchronized by mutx.cpp because most of objects - use their own mutex'. +4.0.0 DIVERSE -sock.cpp - The socket manager. Manages the socket connections. There - are multiplexed sockets. For each requests a new POSIX thread - will be created. +4.1.0 WRITING BUG REPORTS -Files with a leading s_ contain static C++ classes +How to submit a good bug report? -s_chat.cpp - Static wrapper for the dynamic chat class. holds one global - reachable instance of chat until the program shuts down. +Send them to Mail at yChat dot org. -s_conf.cpp - Static wrapper for the dynamic conf class. holds one global - reachable instance of conf until the program shuts down. +First you should give the following information: +- yChat version, if CVS (or devel. tarball) then which day? +- operating system / distribution and it's version +- when did it crash? did you do something? can you reproduce the crash? -s_html.cpp - Static wrapper for the dynamic html class. holds one global - reachable instance of conf until the program shuts down. +Getting backtrace of the crash also helps a lot, especially if yChat crashes +randomly. If after crash you see text: -s_mutx.cpp - Static wrapper for the dynamic mutx class. holds one global - reachable instance of conf until the program shuts down. + "segmentation fault (core dumped)" -s_sock.cpp - Static wrapper for the dynamic sock class. holds one global - reachable instance of conf until the program shuts down. +It writes a file named "core" or "ychat.core" depending on your OS to directory +where you started yChat. If it doesn't print the "(core dumped)" or you can't +find the core file, you'll have to raise the limit for max. core file size +before running yChat. To do this, say: -s_tool.cpp - Static class which includes some usefull global reachable - methods which are not integraded in independent classes. + ulimit -c unlimited -Special header files ( all other header files which are not listed here -belong to their respective .cpp files ): +So, if you have the core file and GNU debugger (gdb), you can get the +backtrace with: -glob.h - Defines global variables which are known by compilation - time. + gdb ./bin/ychat ychat.core + bt -incl.h - This file is included from every other header file and - includes a set of headers which every class should be able - to use. +Paste all the lines starting from line having #0 at the beginning. -msgs.h - Defines console output messages for verbosity level 0 ( see - glob.h for setting up verbosity levels ). and also defines - all the system messages. you may edit this file for translating - the system user language. +Here's an example session: -The basic class structure: + in reqp::parse(thrd*, std::string, std::map, std::allocator > >&) () + (gdb) bt + #0 0x0805c287 in reqp::parse(thrd*, std::string, std::map, std::allocator > >&) () + #1 0x0806060f in sock::read_write(thrd*, int) () + #2 0x080612ba in thrd::run() () + #3 0x0805a3b8 in pool::run_func(void*) () + #4 0x0805a375 in pool::tpool_thread(void*) () + #5 0x281d44ae in _thread_start () from /usr/lib/libc_r.so.5 + (gdb) - base base - | | name - | | / \ - | | / \ - chat room user +If you dont get such a gdb output, you need to recompile the yChat using +debuggig symbols. You can do it this way: - cont - / \ - / \ -conf html +cd ychat +gmake confdebug all run -1.8 CONTACT: +4.2.0 CONTACT ADDRESSES You may contact us through the following addresses: @@ -220,12 +588,24 @@ You may contact us through the following addresses: The yChat homepage is located at http://www.yChat.org - E-Mail - Paul C. Buetow: Snooper@yChat.org ( core developer ) - Volker Richter: Rover@yChat.org ( core developer ) - Mail@yChat.org ( reaches everybody of yChat ) + Paul C. Buetow: buetow at yChat point org ( core developer ) + Mail at yChat dot org ( reaches everybody of yChat ) - ICQ Paul C. Buetow: 11655527 - IRC - #ychat at irc.german-elite.net + #Ychat and #Coding at irc.german-elite.net + + +4.2.0 CREDITS + +Thanks to the following persons. Without them yChat would not be like today: + +- Volker Richter of EXA Digital Solutions GbR + (http://www.exa-ds.com) for adding initial MySQL support and lots of more + code. + +- Joshia Teitelbaum of CryptpMail.org for adding + initial OpenSSL support and lots of security patches in the HTTP header + handling. diff --git a/RELEASES b/RELEASES index a70fede..2cd7a7b 100644 --- a/RELEASES +++ b/RELEASES @@ -1,27 +1,40 @@ Release table -Release date Branch Release focus +Release date Release name and version Release focus -Planing: yChat 0.8-RELEASE Features -Planing: yhttpd 0.8-RELEASE Features -Planing: yxml 0.x-RELEASE Initial release +Planing: ycurses 0.1-RELEASE________ Initial release +Planing: yhttpd 0.8-RELEASE_________ Features +Planing: yChat 0.7.9.4-STABLERELEASE +Planing: yChat 0.8-RELEASE__________ Features -Feb 18th 05 yChat 0.7.6-RELEASE Improvements -Feb 15th 05 yChat 0.7.5-RELEASE Features, bugfixes -Feb 14th 05 yChat 0.7.4.1-RELEASE Bugfix -Feb 12th 05 yChat 0.7.4-RELEASE Bugfixes, improvements, features -Feb 10th 05 yChat 0.7.4-PRERELEASE Bugfixes, improvements, features -Dec 29th 04 yChat 0.7.3-RELEASE Bugfixes, features -Nov 09th 04 yChat 0.7.2-RELEASE Bugfixes, features -Nov 06th 04 yhttpd 0.7.1-RELEASE Bugfixes -Nov 06th 04 yChat 0.7.1-RELEASE Bugfixes -Nov 01st 04 yhttpd 0.7-RELEASE Initial release -Oct 31st 04 yChat 0.7-RELEASE Cleanup, features -Jan 03rd 04 yChat 0.5.1-RELEASE Cleanup, bugfixes -Sep 15th 03 yChat 0.6-RELEASE Cleanup, features -Sep 15th 03 yChat 0.5.0-RELEASE Features -Apr 26th 03 yChat 0.4-RELEASE Features -Mar 30th 03 yChat 0.3-RELEASE Features -Mar 24th 03 yChat 0.2-RELEASE Bugfixes -Mar 20th 03 yChat 0.1-RELEASE Initial release +May 25th 05: yChat 0.8-RELEASE Major features +May 08th 05: yChat 0.7.9.3-STABLERELEASE Security bugfixes +Apr 11th 05: yChat 0.5.5-STABLERELEASE__ Minor security fixes +Apr 10th 05: yChat 0.7.9.2-RELEASE______ Major security fixes +Apr 07th 05: yChat 0.7.9.1-RELEASE______ Minor bugfixes +Mar 11th 05: yChat 0.7.9-RELEASE________ +Mar 08th 05: yChat 0.5.4-STABLERELEASE__ +Mar 05th 05 yChat 0.7.8-RELEASE________ +Mar 02th 05 yChat 0.5.3-LEGACYRELEASE__ +Feb 27th 05 yChat 0.5.2-LEGACYRELEASE__ +Feb 24th 05 yChat 0.7.7.1-RELEASE______ Major bugfixes +Feb 21th 05 yChat 0.7.7-RELEASE________ +Feb 18th 05 yChat 0.7.6-RELEASE________ +Feb 15th 05 yChat 0.7.5-RELEASE________ +Feb 14th 05 yChat 0.7.4.1-RELEASE______ Major bugfixes +Feb 12th 05 yChat 0.7.4-RELEASE________ +Feb 10th 05 yChat 0.7.4-PRERELEASE_____ +Dec 29th 04 yChat 0.7.3-RELEASE________ +Nov 09th 04 yChat 0.7.2-RELEASE________ +Nov 06th 04 yhttpd 0.7.1-RELEASE_______ +Nov 06th 04 yChat 0.7.1-RELEASE________ +Nov 01st 04 yhttpd 0.7-RELEASE_________ Initial release +Oct 31st 04 yChat 0.7-RELEASE__________ +Jan 03rd 04 yChat 0.5.1-RELEASE________ +Sep 15th 03 yChat 0.6-RELEASE__________ +Sep 15th 03 yChat 0.5.0-RELEASE________ +Apr 26th 03 yChat 0.4-RELEASE__________ +Mar 30th 03 yChat 0.3-RELEASE__________ +Mar 24th 03 yChat 0.2-RELEASE__________ +Mar 20th 03 yChat 0.1-RELEASE__________ Initial release diff --git a/TODO b/TODO index d20d2b1..c0c0a28 100644 --- a/TODO +++ b/TODO @@ -1,41 +1,42 @@ -Might do's for next RELEASE: -- Remove Chat stuff from yhttpd.conf -- dir : public vector -- Disable /help command for commands wich are not accessible for the - specific user. -- Flood protection -- Add /nick, /beam, /su -- Add / to whisper to the last person to whom the user has been whispered the last time. -- Room maxuser limit. +- Must do's for next RELEASE - +$ None specific -To do in general for some later RELEASE: -- Not found sites should get a 404 error site! -- Implement dynamic timer -- Implement ncurse object browser -- Implement yXML subproject -- Implement ODBC support -- Implement login counter. -- Implement msg post counter. -- Implement online time counter. -- Implement hall of fame rankings of the counters above. Also add a msg/minute hall of fame. -- Implement traffic stats -- Implement more chat commands -- Implement new dynamic command permission method -- Implement SSL sockets with OpenSSL -- Implement user profiles -- Implement action form to input.html -- Implement IRC support -- Implement possibility sending Mails through external SMTP server (for password reminder etc) -- Implement chat moderator option -- Implement several HTML styles, each user can use his favourite style -- Implement compatibility to Opera, Links, Konqueror and Safari -- Implement browser side caching for gfx files support -- Disable http-refresh of the online frame. Reload it only if there has been s.t. changed. -- Implement a http:// url detection and make a link out of it! -- Remove user.cpp member variables as possible and replace them with hash maps - for (integer,mutex) and (string,mutex) pairs. Maybe use s.t. like this: - p_user->val("name"); to get the users name and p_user->val("name","val"); to - reset his name. Maybe use templates to get different types besides strings: - p_user->val("hits"); -- Write changes of the configuration back into XML if wished. +- Might do's for next RELEASE - +$ Add thread pool decreasing +$ dir : public vector +$ Disable /help command for commands wich are not accessible for the +$ specific user. +$ Flood protection +$ Add /nick, /beam, /su +$ Add / to whisper to the last person to whom the user has been whispered the last time. +- Known bugs - +$ Using yChat via proxy sometimes causes a white chat stream. This might be +$ resolved by implementing last modified and current time/date informations +$ into the HTTP header. + +- To do in general for some later RELEASE - +$ Use libevent +$ Implement a switch so that all dynamic dlopen modules can be compiled within the yChat executable not using dlopen. +$ Implement dynamic timer +$ Implement ncurse object browser +$ Implement yXML subproject +$ Implement ODBC support +$ Implement login counter. +$ Implement msg post counter. +$ Implement online time counter. +$ Implement hall of fame rankings of the counters above. Also add a msg/minute hall of fame. +$ Implement traffic stats +$ Implement more chat commands +$ Implement new dynamic command permission method +$ Implement user profiles +$ Implement action form to input.html +$ Implement IRC support +$ Implement possibility sending Mails through external SMTP server (for password reminder etc) +$ Implement chat moderator option +$ Implement several HTML styles, each user can use his favourite style +$ Implement compatibility to Opera, Links, Konqueror and Safari +$ Implement browser side caching for gfx files support +$ Implement a http:// url detection and make a link out of it! +$ Remove user.cpp member variables as possible and replace them with hash maps +$ Write changes of the configuration back into XML if wished. diff --git a/configure b/configure index 8c5f0a7..9aab971 100755 --- a/configure +++ b/configure @@ -1,1555 +1,77 @@ -#! /bin/sh +#!/bin/sh -# Guess values for system-dependent variables and create Makefiles. -# Generated automatically using autoconf version 2.13 -# Copyright (C) 1992, 93, 94, 95, 96 Free Software Foundation, Inc. -# -# This configure script is free software; the Free Software Foundation -# gives unlimited permission to copy, distribute and modify it. - -# Defaults: -ac_help= -ac_default_prefix=/usr/local -# Any additions from configure.in: - -# Initialize some variables set by options. -# The variables have the same names as the options, with -# dashes changed to underlines. -build=NONE -cache_file=./config.cache -exec_prefix=NONE -host=NONE -no_create= -nonopt=NONE -no_recursion= -prefix=NONE -program_prefix=NONE -program_suffix=NONE -program_transform_name=s,x,x, -silent= -site= -srcdir= -target=NONE -verbose= -x_includes=NONE -x_libraries=NONE -bindir='${exec_prefix}/bin' -sbindir='${exec_prefix}/sbin' -libexecdir='${exec_prefix}/libexec' -datadir='${prefix}/share' -sysconfdir='${prefix}/etc' -sharedstatedir='${prefix}/com' -localstatedir='${prefix}/var' -libdir='${exec_prefix}/lib' -includedir='${prefix}/include' -oldincludedir='/usr/include' -infodir='${prefix}/info' -mandir='${prefix}/man' - -# Initialize some other variables. -subdirs= -MFLAGS= MAKEFLAGS= -SHELL=${CONFIG_SHELL-/bin/sh} -# Maximum number of lines to put in a shell here document. -ac_max_here_lines=12 - -ac_prev= -for ac_option -do - - # If the previous option needs an argument, assign it. - if test -n "$ac_prev"; then - eval "$ac_prev=\$ac_option" - ac_prev= - continue - fi - - case "$ac_option" in - -*=*) ac_optarg=`echo "$ac_option" | sed 's/[-_a-zA-Z0-9]*=//'` ;; - *) ac_optarg= ;; - esac - - # Accept the important Cygnus configure options, so we can diagnose typos. - - case "$ac_option" in - - -bindir | --bindir | --bindi | --bind | --bin | --bi) - ac_prev=bindir ;; - -bindir=* | --bindir=* | --bindi=* | --bind=* | --bin=* | --bi=*) - bindir="$ac_optarg" ;; - - -build | --build | --buil | --bui | --bu) - ac_prev=build ;; - -build=* | --build=* | --buil=* | --bui=* | --bu=*) - build="$ac_optarg" ;; - - -cache-file | --cache-file | --cache-fil | --cache-fi \ - | --cache-f | --cache- | --cache | --cach | --cac | --ca | --c) - ac_prev=cache_file ;; - -cache-file=* | --cache-file=* | --cache-fil=* | --cache-fi=* \ - | --cache-f=* | --cache-=* | --cache=* | --cach=* | --cac=* | --ca=* | --c=*) - cache_file="$ac_optarg" ;; - - -datadir | --datadir | --datadi | --datad | --data | --dat | --da) - ac_prev=datadir ;; - -datadir=* | --datadir=* | --datadi=* | --datad=* | --data=* | --dat=* \ - | --da=*) - datadir="$ac_optarg" ;; - - -disable-* | --disable-*) - ac_feature=`echo $ac_option|sed -e 's/-*disable-//'` - # Reject names that are not valid shell variable names. - if test -n "`echo $ac_feature| sed 's/[-a-zA-Z0-9_]//g'`"; then - { echo "configure: error: $ac_feature: invalid feature name" 1>&2; exit 1; } - fi - ac_feature=`echo $ac_feature| sed 's/-/_/g'` - eval "enable_${ac_feature}=no" ;; - - -enable-* | --enable-*) - ac_feature=`echo $ac_option|sed -e 's/-*enable-//' -e 's/=.*//'` - # Reject names that are not valid shell variable names. - if test -n "`echo $ac_feature| sed 's/[-_a-zA-Z0-9]//g'`"; then - { echo "configure: error: $ac_feature: invalid feature name" 1>&2; exit 1; } - fi - ac_feature=`echo $ac_feature| sed 's/-/_/g'` - case "$ac_option" in - *=*) ;; - *) ac_optarg=yes ;; - esac - eval "enable_${ac_feature}='$ac_optarg'" ;; - - -exec-prefix | --exec_prefix | --exec-prefix | --exec-prefi \ - | --exec-pref | --exec-pre | --exec-pr | --exec-p | --exec- \ - | --exec | --exe | --ex) - ac_prev=exec_prefix ;; - -exec-prefix=* | --exec_prefix=* | --exec-prefix=* | --exec-prefi=* \ - | --exec-pref=* | --exec-pre=* | --exec-pr=* | --exec-p=* | --exec-=* \ - | --exec=* | --exe=* | --ex=*) - exec_prefix="$ac_optarg" ;; - - -gas | --gas | --ga | --g) - # Obsolete; use --with-gas. - with_gas=yes ;; - - -help | --help | --hel | --he) - # Omit some