home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.databases.sybase
- Path: sparky!uunet!tekbspa!tssgate!esh
- From: esh@prague.tss.com (Edward S. Hirgelt)
- Subject: Re: SUMMARY - Notifying clients of table mods
- In-Reply-To: fgreco@shearson.com's message of Thu, 7 Jan 1993 14:52:00 GMT
- Message-ID: <ESH.93Jan8105010@prague.tss.com>
- Sender: news@tss.com (USENET Network News)
- Organization: Teknekron Software Systems, Inc.
- References: <1993Jan7.145200.12137@shearson.com>
- Date: Fri, 8 Jan 1993 18:50:10 GMT
- Lines: 37
-
-
- On Thu, 7 Jan 1993 14:52:00 GMT,
- fgreco@shearson.com (Frank Greco) said:
-
- [Nice summary of client's notification when a table is modified deleted.]
-
- Frank> There are other places in dblib where the dataserver calls your
- Frank> own specified routines (e.g., message/error handling); it'd be
- Frank> nice if there was some mechanism to allow triggers (and
- Frank> alerters ... hint... hint) to do this *directly* in Sybase.
-
- Hmmm, let me try to clear up what seems to be a subtle point.
-
- The dataserver does NOT call a routine in the client's process space.
- Your message handler is invoked bu dblib when the server sends your
- application a message using the standard TDS protocol (Tabular Data
- Stream). This is a very synchronous operation. Your application issues a
- query which results in some reply. The reply can be data (rows returned)
- or informative or error messages. The latter trigger callbacks. DB
- Library (OpenClient) in interpreting the data fires your callback, not
- the server.
-
- Like I said this is a subtle and pedantic point. However it makes clear
- why no other client will be informed. The communication is point to
- point.
-
- This is why the OpenServer or ToolTalk (very nicely done btw) or some
- sort of polling in general is the solution.
-
- Hope this helps clarify things.
-
- Ed
-
- --
- Ex vitio alterius |Ed Hirgelt |esh@tss.com
- sapiens emendat suum. |Teknekron Software Systems, Inc|
- (Publilius Syrus) |Palo Alto, Ca. |
-