Re: [VANILLA-LIST:2150] cow stuff in the vanilla configure

[Keir.Morgan@Eng.Sun.COM (Keir Morgan)]

[...]

Krut and James spat:

> >Can we split the two things out?
> 
> In earlier time the server and client used a lot of common
> defs files, which always guarantied, that both are in sync.
> As a result of splitting things up, COW for ex. recently had
> a bug that it crashed on phasered plasmas because someone
> added some new whydead enums without notifying the client
> development.
> 
> So I vote for merging more things, maybe even generating common
> libraries instead of splitting up everything completely.
>
> In particular all the C/S protocol stuff should be definitely
> in a common file.
 
  Common libraries would be great. 

  However, what might work as a start is a common directory (say
export) that is built as part of the server which contains all
publicly external interfaces that the client (or other programs,
say xsg?) might use. Naturally, we'd some sort of heirarchy within
this subdirectory -- lib and include immediately come to mind,
though I'm sure there would be others.

  Client developers wouldn't have to deal with a full version
of the server, just the -current "exported" interfaces which could
easily be put in CVS or available via "binary/pkg/RPM" distribution.

  I'd volunteer to do this work but, I'm currently neck deep with
work and a merge between a version of Sun's internal server and the
current vanilla (lots of diffs). 

  Anyway, hopefully the above makes some sense.

Cheers,

Keir
--