instead of a full on chat (or until there is one) a "fake chat" where a PM thread is listed, using ajax to do updates and sends.. a "chat" icon in the options list maybe, or a "chat" button next to "reply" in the retrieved post

It would be a Plugin but its possible however it would be quite resource intensive

Does Paul know about the chat script yet?

I just started working on the shoutbox/chat (whatever you want to call it).  Once I finish the standalone I will be integrating it into the cms as a plugin.  This should be done within a few days if none of my other jobs get in the way.

Edit:  I have finished the stand alone version.  I plan on making this a few ways so that the site admin has good control over everything.  I plan on making it so it can be either txt file based or mysql based.  The txt file system will be good for small sites but it has its downfalls as well.  It has no log of messages other then what is currently displayed as well as a few others.  The mysql way will provide better logging of messages as well as the ability for an admin to search for a specific users messages.  As I go I will probably find more and more features to add.  I hope to have a demo up soon.

i take it that this will be able to have on my own site if i download the plugin from the SVN?

Yes and no.  Yes you will be able to have it on your own site, but no because it should not be in the svn as it is a plugin.  It should be downloadable from wherever it is hosted at (eg. if I make it, it will be hosted at GarbageSpot along with my other projects and plugins.  Once the mods database it set up it will be available there as well.

ahh ok why doesnt eocms just get a live feed to the database so when a plugin is released on eocms then you have the option to send it out to everyone who is using the cms on there site

Who says everyone wants to know about every update to the plugins database.  Even more so if it gets popular.  People usually know what plugins they are looking for and can search it accordingly when they need to.

if the plug-in can show "updated", then they could probably show "new", but that may be better in a small (subscribed) panel in the plugins (as an option), or as part of a "customization notifer" plugin

the plugins page could have a link to the plugins section of the mods url though.. "get new plugins" (or something)

but it could be like a popup on your own site which sayes that a update has comeout and then gives you the option to add it to ur site but eocms have the control on what plugins to send out

I think that this could be an option that could be enabled for each plugin.  Not as a default though, it seems to be a lot of checking for little to no gain for each plugin.  I guess it all depends on how much each plugin gets updated.

hmm true i never thought of that

I am willing to make a eoChat plugin when its done

I am currently converting my standalone to a plugin, but if you would like to give it a go feel free.   It is a pain in the ass though, I will give that as a forwarning.  I am trying to make it feature rich, database or flat file driven, as well as easy to use.  So far it works stand alone in a flat file and that is it.  I have integrated the standalone into the cms but am still working on all of the sql.  Once that is done it should easily be able to work on either flat file or databases. 
Again though, if you want to give the conversion a shot, ill clean up my source code and send you a copy. (Note: you will want to be good in php, ajax, javascript, and possibly sql.  It is very ajax/javascript driven.)

eoChat uses COMET to update the chat, and a PHP/MySQL Backend

just a note here, 110mb does not "condone" php based chats..

My chat system I made is based on the ajax refresh shoutbox.  It has a refresh rate that can be changed (default is 3 seconds) between any updates.  So sending/recieving/updating users online are all done in that three second cycle.

The last time I checked that was allowed on 110mb even if it had the php/mysql or php/txt file backend.

I think it was a server request per second thing, if you set the default time to something within 110mb "limits" it should be OK (this is if its packaged up with the 110mb one-click-install)

I don't see the chat being integrated with the base install as it would add unnecessary bloat.  As a mod that can be installed by the user, yes.  I dont see the need to have this on every site, or many sites for that matter.  This will then impose on the user the responsibility of setting the proper times.  I honestly think somewhere between three to five seconds should not cause to much strain (but different hosts see things differently).

yeah, my thoughts also..

3-5 depending on # of users. This is where a java and or irc based chat unloads the (target web) server

ok, so I think there is a valid need for the original request in this thread, that is not refresh related, but PM linked, and to start of with at least, is just user to user. group "chat" (thread) could be added after.. (I just wanted something simple and PM was there, and "long" PM threads was what I was dealing with at the time - we were both online)..

I'll have a look at this, as it comes under the sections of "plugin/addon requires modifing current eoCMS default output/functions process", and thats tied to the new -info files I've been trowing around the board lately (they work well BTW)