Broadcast (OpenInsight 32-Bit)
At 15 JUN 2006 08:01:27AM Kauko Laurinolli wrote:
Any possibilities in v7.2.1 for Administrator to send a broadcast message to to all user screens logged to the program?
At 15 JUN 2006 09:09AM Mike Ruane wrote:
Kauko-
No, sorry. However, I was looking at that functionality for the UD Heavy or UD 3.1. We weren't able to get it in yet, but it's still something that I would like to do in a future release.
Thanks-
Mike Ruane
At 15 JUN 2006 09:14AM John Bouley wrote:
How about looking at the SysLogins and extracting a list of Stations or Users. Then issuing the appropriate OS Send Message? I looked at Windows and it is expecting the User so your OI Users would have to match the Network users.
John
At 15 JUN 2006 09:15AM Gerald Lovel wrote:
If your application has a main MDI frame, and a TIMER is placed on the frame, and a timer program checks for messages posted to a control, and the administrator updates the control, then YES. This is not dependent on the OI version.
At 15 JUN 2006 08:33PM Kauko Laurinolli wrote:
Unfortunately all my users log in under the same OI user ID (I have spun my own security system) so OI usernames and network user names will not match.
At 15 JUN 2006 09:07PM dsig@sigafoos.org wrote:
It still isn't a big deal .. as suggested before put a timer on your 'primary' screen' (most likely a mdi).
Then let it check some really cool file for any messages.
find who the message is to and if it is the current user give them the message
At 16 JUN 2006 01:47PM Pascal Landry wrote:
If you know the users IP and TCP/IP port or named pipe, you can create a process to attach to each and execute a message or window from a stored procedure.
I made one a while ago that would start a window with three pictures of myself that would change every second. I sometimes start it up when I want users to call me.
Unfortunately, you can only connect to one at a time.
Pascal
At 16 JUN 2006 02:19PM dbakke@srpcs.com's Don Bakke wrote:
As a proof of concept we developed an OI-based instant message utility which use a remote engine running on a server. Each chat "client" would send messages to the engine and it would hold this information in named common variables. Then each client would poll the engine (using the TIMER event) to check for any messages. It worked, but after several clients were running it would slow the system down very noticably.
This is similar to the techniques that have been suggested where a record is written to a table. However, for instant message based functionality we wanted to minimize the disk I/O. We also have an OI-based "mail" system that uses tables to store data and then send notifications to each user who has an unread message.
At the present we are working on a project that will provide true instant messaging features for OI. This will be commercially available so if you are interested in more information please drop us a line.
dbakke@srpcs.com
