Instant Messaging groups
-
There's always the option of using a public Microsoft NetMeeting server and putting a meeting password on.
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1
K. Brian Kelley
@kbriankelley -
Jabber (www.jabber.org) an open source IM tool could be the answer. Jabber is a xml based IM which gives a lot of flexibility at client and server end to do whatever you want. While the server can be programmed to log relevant IM exchanges, a SQLServerCentralJabber client can be created which regulates chat sessions.
JabberCOM (http://jabbercom.sourceforge.net/) eliminates even the need to understand the client protocol. Entry to the IM server can be restricted to SQLServerCentralites and interruptions to work avoided by creating a "Busy" status setting ("Presence" in Jabber terminology) on the client which ensure that messages are not sent to the particular client.
This is my first post on this forum, so kindly excuse if this is load of gibberish.
Narayanan
-
Interesting - we'll take a look.
Andy
-
If/when you host a chat session, can you take us Southern Hemisphere guys into account when you set the time.
I'm not that good in the wee early hours of the morning
Thanks
Phill Carter
--------------------
Colt 45 - the original point and click interface
-
Our wee hours or yours?
We'll do our best!
Andy
-
I think the idea of using an IM type of environment would certainly be of benefit.
I would prefer a more collaborative social place for DBA's where they could bounce questions off of one another or offer advice, but only between DBA's, not the general public that just installed an RDBMS and need beginner help.
Just my two cents or three.
Viewing 6 posts - 16 through 20 (of 20 total)
You must be logged in to reply to this topic. Login to reply