123-Flash-Chat-Server-Software 6.9 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News 123-Flash-Chat-Server-Software 6.9 (Default branch)
# 1  
Old 01-17-2008
123-Flash-Chat-Server-Software 6.9 (Default branch)

Image 123-Flash-Chat-Server-Software is a full-featured chat server for high-load websites. It features a range of customization options, can be smoothly integrated with the database of almost any popular portal or forum system including Joomla!, phpBB, PHP-Nuke, and PostNuke, includes plain text chat and video chat options, and is scalable enough to fit the needs of small business and large enterprises. License: Shareware Changes:
This release features an optional Chat Room Remote Controller (MSN edition), which allows chat room moderators to keep an eye on the chat room from anywhere. An "init_avatar" parameter was added to the optional avatar chat module to pre-define the gender of the user avatar. Four cool choices are provided. The admin panel was improved.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
NAGZILLAC(1)						      General Commands Manual						      NAGZILLAC(1)

NAME
nagzillac - jabber relay bot client SYNOPSIS
nagzillac type^JID^message DESCRIPTION
This manual page documents briefly the nagzillac command. nagzillac is the client for nagzilla that takes the data you hand it as argument and sends it over to the nagzilla daemon that will send the message along. OPTIONS
nagzillac only takes one options that consists of three arguments. They are seperated by the carret character(`^'), although the last argu- ment may contain carrets without any troubles. Here is an explenation of the different parts: type This is the type of the message. It can be either room (which will send the message to a jabber conference room) or chat (target should be a jabber ID). JID This is the target for the message. If you choose room type it has to be a conference room name or complete ID. A single room with- out any @ in it will get sent to the configured conference server. If you choose the chat type the JID has to be the jabber ID of the user to receive the message, either just the user part which will get added the jabber server as domain part, or a full jabber ID. message The final part is the message that will get sent. At the moment it will be put into the body as plain text. Please notice that you will have to quote or escape special characters in the message like white space. FILES
/etc/nagzillac/nagzillac.cfg The configuration file for the nagzilla client. Please see the comments in the file for informations on what to tweak. EXAMPLE
The following sends a chat message to the rhonda user on the default server: nagzillac "chat^rhonda^hi there" This will send a message to a conference room on a different server: nagzillac "room^monitor@jabber.doma.in^alert - do something" SEE ALSO
nagzillad(1). AUTHOR
nagzillac was written by Bill Mathews. This manual page was written by Gerfried Fuchs <rhonda@debian.at> for the Debian project (and may be used by others). 2009-06-03 NAGZILLAC(1)