[comp.protocols.appletalk] CAP6.0 --- problems & future directions

majumdar@garnet.cs.yale.edu (aloke majumdar) (04/25/91)

	We've had CAP6.0 running native ethertalk on a SPARC 1 (SunOS 4.1) for
several weeks now and I'm quite happy with it in general. We've done some stress
testing on it and hope to have some benchmark figures compiled in a couple of
weeks. I'll post those to the net when they're available.

	Right now I have some queries about future CAP directions and some notes
on problems with the current release.

1) Is work being done on getting CAP to work with ethertalk phase 2? I'd be
willing to contribute my time to getting it done, but I don't want to start from
scratch if someone already has a lot of code that they haven't got around to
finishing. This is going to be increasingly important in the coming months as
more and more people make the switch.

2) I've had complaints from a user about PC Appleshare not being able to mount
AUFS. So far I haven't got any followup details, but I wondered if other people
have had the same problem.

3) Have the patches to "lwsrv" to capture the new style laserprep (with split
AppleDicts) been folded into the release? Incidentally, we got "lwsrv" to work
with an LPS40 hosted by a VAX/VMS machine, but I had to use a modified AppleDict
in order to do so. I haven't yet had to modify the latest version(s) of the
laserprep, but will inevitably have to do so in the next couple of months.

4) I'd heard that Apple had bought the rights to CAP (whatever that means). Is
there any truth to this? If so, how is it going to effect those of us who have
started on relying on this superb piece of net-supported software? Will future
versions have to be purchased from Apple? Are they going to continue supporting
software that runs on other vendor's machines? etc.


Aloke Majumdar
Yale Computer Center

coolidge@cs.uiuc.edu (John Coolidge) (04/28/91)

majumdar@garnet.cs.yale.edu (aloke majumdar) writes:
>	Right now I have some queries about future CAP directions and some notes
>on problems with the current release.

>[Queries deleted]

I'd also like EtherTalk phase 2 compatibility (I could move the server
off my A/UX machine and onto someone else's SparcStation :-)); even more
important for me is the option to save AUFS files as AppleSingle or
AppleDouble documents rather than the massive hackage CAP uses now.
We've got lots of A/UX boxes around, and it's a massive pain having big
directories full of AppleSingle/Double files and big directories full of
CAP files, none of which can speak to each other without translation.
I'd prefer to use the same disk space for both, and I'd prefer it to be
in AppleSingle/Double format since native file reading is much faster
under A/UX than CAP AUFS access.

--John

--------------------------------------------------------------------------
John L. Coolidge     Internet:coolidge@cs.uiuc.edu   UUCP:uiucdcs!coolidge
Of course I don't speak for the U of I (or anyone else except myself)
Copyright 1991 John L. Coolidge. Copying allowed if (and only if) attributed.
You may redistribute this article if and only if your recipients may as well.

djh@cs.mu.oz.au (David Hornsby) (05/01/91)

majumdar@garnet.cs.yale.edu (aloke majumdar) writes:
> 1) Is work being done on getting CAP to work with ethertalk phase 2?

Yes.

> 2) I've had complaints from a user about PC Appleshare ...

The PC AppleShare support needs to be configured in at Configure time.
Uncomment the "SHORT_NAMES" definition in the features file. This will
probably merge permanently into the code in a future CAP release.

> 3) Have the patches to "lwsrv" ... been folded into the release?

There are a bunch of contributed feature patches waiting to be folded
in, this is one of them (BTW this week is the deadline for any new code
submissions). The current plan is to release a number of patches with
the new stuff all at once. If there are no problems then CAP 6.1 will
appear a short time later. The original time frame for this was mid May,
but Phase 2 testing will probably delay things by a couple of weeks or
so (but the wait should be worth it).

 - David.