[OpenAFS] AFS Perl API bos & vos requirements (resend)

[Jenkins, Steven]

Is your concern a naming issue?  Ie, would you be more comfortable to
see the library named libvos_client.a? =20

Steven

-----Original Message-----
From: Chaskiel M Grundman [mailto:cg2v@andrew.cmu.edu]=20
Sent: Friday, May 02, 2003 11:14 AM
To: OpenAFS Info
Subject: Re: [OpenAFS] AFS Perl API bos & vos requirements (resend)


--On Friday, May 02, 2003 10:52:34 +0200 Norbert Gruener
<nog@MPA-Garching.MPG.DE> wrote:

>> - put all of vos.o except the main() into libvos.a, as well as
>>   volint.ss.o & volint.cs.o, and then verify that vos still works.
That
>>   would primarily be some build hacking.
>=20
> Do you think that you can convince the OpenAFS developers to do that
> step ?   If so, I will be happy. =20

This seems somewhat poorly thought out. The stuff in vos.c is very much
front-end oriented. The functions which take only a struct cmd_syndesc
*as are command parsers for vos. They are not library functions. They
call some utility functions to set things up, and then one of the UV_ or
VLDB_ functions from libvolser.a/libvldb.a to do the actual work. I
suppose that it might make sense to put things like WriteData,
DumpFunction, and their dependencies into a library. but not the rest of
vos.c. (if you were considering calling GetServer or cmd_Dispatch from
xs code, then, IMO, you aren't really writing a perl api for the volser
library, but something else. There are serious issues with the volser
client code, but this isn't one of them)



_______________________________________________
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info