|
A1)
Yes, By setting the values for 'UserName' and 'RoomName' you can read user
settings from wherever they are located (e.g. Session, cookies, database,
QueryString etc)
|
|
A2)
Yes, this can be done via the function GetRoomUsage() available from any
instance of a JaxterChat object. This function returns a dataset containing the
room name, the number of users, and a list of the users for each room as data
columns which may be bound to a DataGrid / GridView etc.
|
|
A3)
Yes, JaxterChat is compatible with ASP.NET 1.1, ASP.NET 2.0 and ASP.NET 3.5 but
is not fully supported by the free Visual Web Developer. In the case of VWD,
you must manually copy in the JaxterChat resources directory to the root of
your website and you will not have designer preview available.
|
|
A4)
Yes, JaxterChat was built with cross-browser compatibility in mind and tested
on Internet Explorer 6, Mozilla Firefox 1.5 (Mac and Win), Opera 9, Safari 1.3.
Appearance of control and performance may vary slightly between browsers. (N.B.
Scrollbar styles apply to Internet Explorer only, other browsers will adopt the
native scrollbar appearance)
|
|
A5)
JaxterChat incorporates advanced client-side logic to overcome these issues.
Asynchronous AJAX calls combined with this client side performance increase
means JaxterChat will perform almost as well as stand-alone chat clients.
|
|
A6)
JaxterChat can be deoployed to a remote web server as simply as copying the
files across via ftp. There are no extra permissions required by the control.
|
|
A7)
No. There is no need for a database at all to run JaxterChat on your website.
Configuring databases and the associated permissions can be very time
consuming, especially when dealing with a 3rd party service provider. Other
non-database solutions such as XML persistance have experienced slow
performance and lost updates due to concurrency concerns. JaxterChat utilises
optimised server caching and a stateless communication protocol to replace the
need for a database.
|
|
A8)
Yes, a server side event 'MessagePosted' is provided for this purpose. From
this event handler you have access to the message details and may implement
whatever custom logging solution you like. An example of this event being used
to log to a text file can be found in the development guide included with the
control.
|
|
A9)
While it is not a requirement, Java is used for playing sounds via the chat if
the Java plug-in exists on the client's pc. The sound player applet used by
JaxterChat is compiled in an older version of Java so any browser that has ever
had Java installed should be compatible. If the client does not have Java
enabled, then they will simply not hear any sounds while using the chat and the
sound icon on the interface will be disabled. The sound toggle can be switched
off via a designer property if the website creator wishes disable sound
entirely.
|
|
A10)
Yes, with only a few lines of code, you can broadcast to some / all chat rooms
any html content you wish from within your web application.
WebFurbish.JaxterChat myChat = new WebFurbish.JaxterChat();
myChat.SendCustomMessage("news flash 123", "Admin Bot", "MyRoomName", false);
|
|
A11)
No. JaxterChat utitilises Application state for storage of message buffers. In
a load balanced server farm environment, this Application state is not
persisted and the chat will not work. This feature will be included in an
upcoming database enabled edition of JaxterChat
|