Title: | DECWINDOWS 26-JAN-89 to 29-NOV-90 |
Notice: | See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit |
Moderator: | STAR::VATNE |
Created: | Mon Oct 30 1989 |
Last Modified: | Mon Dec 31 1990 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 3726 |
Total number of notes: | 19516 |
I am thinking about modeling decwindows client/server interactions at the X-protocol exchange level as part of another project. I need to know how the events, replies, and requests interact and how the buffering of these take place in the server and client nodes. It might also be neccessary to put some kind of system resource cost on each of these transactions. I am not to terribly sure if this is feasible in any reasonable time frame or if it has perhaps been done before. Where could I go get the kind of information I will need for this?? Any insight would be appreciated... Thanks, Mike Moser
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
1680.1 | Some ideas | RAINBO::HARRIS | Repeal the law of gravity: Juggle! | Tue Nov 07 1989 08:43 | 16 |
You might start with the VMS DECwindows Transport Manual (aa-pabwa-te) which describs how to write your own transport (I think it is available with the internal field test kits for VMS V5.3). This is the section of code between the network and the xlib or server (depending on which hat your wearing at the time). There is also example code DECW$EXAMPLES:XPORT_EXAMPLE.B32. This code actually handles the X-message. Now this doesn't really tell you the interactions, but it does show how the I/O is performed and set up for full async operation. Then I think XLiddy may show you what is actually happening, but since I haven't actually used it, this is only speculation. I'm sure you can get better ideas from experienced users and developers. | |||||
1680.2 | KOBAL::VANNOY | Jake VanNoy | Tue Nov 07 1989 15:55 | 2 | |
Talk to Dinesh Mirchandani in VMS performance. | |||||
1680.3 | Check out XLIDDY/XWOODWARD source | DUGGAN::GABRIEL | Bo knows Motif ?? | Wed Nov 08 1989 09:15 | 12 |
I think both XLIDDY.C and XWOODWARD.C will help out. Do a dir/title=xliddy on either this conference or the old one for pointers to the source. Also, O'Reilly and Associates have a book out titled the X Protocol and it is filled with information about what types of messages are going back and forth between the server and client. Have fun, /Joe |