Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM Enhancement Requests and Suggestions » View Thread |
Messages 1 to 4 of 4 total |
"Admin Maintenance" Mode |
Fri, Jul 28 2006 6:05 PM | Permanent Link |
"Johnnie Norsworthy" | It would be very nice to have the capability to:
Log in as administrator to the ElevateDB server. Send all logged in sessions a text message such as "server will be down in 5 minutes", having it fire a session event with the message on the client (a messaging API would be so cool for C/S stuff) Start "Admin Maintenance Mode". Close all open sessions except administrator to allow database maintenance and not allow any new connections When administrator is done, leave "Admin Maintenance Mode" - everything back to normal. -Johnnie |
Sun, Jul 30 2006 1:31 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Johnnie,
A messaging layer is on the list for the second tier of features that we want to introduce into ElevateDB after the initial release. -- Tim Young Elevate Software www.elevatesoft.com |
Sun, Jul 30 2006 4:28 PM | Permanent Link |
"Johnnie Norsworthy" | "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:A69C7D26-9992-4046-8191-60BF98A5D4FF@news.elevatesoft.com... > Johnnie, > > A messaging layer is on the list for the second tier of features that we > want to introduce into ElevateDB after the initial release. Cool. OK, then maybe I'll stop reading all this stuff about TCP sockets I was filling my brain with the last couple of days. I was thinking it could easily be done with v4, all I need to do is put a TCP server component on the client side to listen for the messages and a single client socket on the server. Then I could use a server-side procedure to iterate through all active sessions and send the message to each, disregarding any non-delivery. The same mechanism could be used to signal database/table changes. It would be nice if the clients that wanted to listen got an event when things of importance happened on the server. -Johnnie |
Mon, Jul 31 2006 9:04 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Johnnie,
<< Cool. OK, then maybe I'll stop reading all this stuff about TCP sockets I was filling my brain with the last couple of days. >> Don't let me stop you from learning something new. << I was thinking it could easily be done with v4, all I need to do is put a TCP server component on the client side to listen for the messages and a single client socket on the server. Then I could use a server-side procedure to iterate through all active sessions and send the message to each, disregarding any non-delivery. The same mechanism could be used to signal database/table changes. >> I think you've got the components backwards - what you want is a server socket on the server and a client socket on the client. Have the client connect to the server port, and then sit back and wait forever on anything that comes from the server. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Tuesday, September 17, 2024 at 04:19 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |