[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

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

2382.0. "XServer Release mismatch?" by FRSTSC::ERLEMANN (Bedman strikes back) Fri Mar 02 1990 09:14

Hi,

a customer of mine claims about the protocol and release versions of the 
Xserver.
He has written a neat C-Program, which checks this items, but gets an unex-
pected value for the protocol version. He expects to get the value 3 or 4
which should be the actual one, but gets 11.

Perhaps try it.

Thanx in advance for any help.

	  <>Armin<>


@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@


/*
    $DEFINE X11 DECW$INCLUDE
    $CC TEST
    $LINK TEST,SYS$INPUT/OPT
    SYS$SHARE:DECW$XLIBSHR/SHARE
    ^Z
*/

#include <stdio.h>
#include <X11/Xlib.h>

main ()
{
Display *xdisplay;
char    *vendor;
int     vendorrelease;
   xdisplay = XOpenDisplay("\0");
   if (xdisplay == 0) {
      printf ("Error opening X_Display\n");
      exit(-1);
   }
   vendor = ServerVendor(xdisplay);
   vendorrelease = VendorRelease(xdisplay);
   printf ("Vendor %s, Release %d\n", vendor, vendorrelease);
}

T.RTitleUserPersonal
Name
DateLines
2382.1FWIWBLOCKP::nethCraig NethFri Mar 02 1990 10:0712
FWIW, here's what the program returns from the Server on my DS3100:

   Vendor DECWINDOWS DigitalEquipmentCorporation UWS2.2, Release 1

Here's what it says on a VMS system running VMS V5.2:

   Vendor DECWINDOWS DigitalEquipmentCorp., Release 11

There seems to be some mismatch between the customer's expectations and
what got implemented....  

2382.2HistoryDECWIN::FISHERBurns Fisher 381-1466, ZKO3-4/W23Tue Mar 06 1990 15:4117
    Back when the protocol was being defined, I convinced Bob Scheifler to
    add a protocol version and a vendor version to the protocol startup.
    They did that, but they insist that the protocol does not change. 
    Therefore, the protocol version is 11 (i.e. X11 as opposed to X10).
    The 3 and 4 that the customers are expecting correspond to MIT's
    release numbers.  Theoretically, the protocol itself does not change
    between MIT releases.  It's just that the server has implemented things
    slightly differently, or added new optional features, etc.
    
    Personally, I think this is sticking the head in the sand.  They should
    have built in a mechanism for evolving the protocol.  However, this is
    what we got.  All X11 servers in the known universe will return 11 as
    the version, thus making my hard-fought battle irrelavent.  (I guess it
    was a case of, "Sure we'll put this in just to shut Burns up..."
    
    Burns