🚀 go-pugleaf

In article <1990Sep14.093420@apollo.HP.COM>, mishkin@apollo.HP.COM (Nathaniel Mishkin) writes:
> 
> >Another problem with NCS approach is that the user cannot take advantages
> >out of any of the new performance improvements of any of the transports.
> >They will have to wait for the NCS team to hack those same fixes into their
> >software.  In ONC, they need not do anything.
> 
> Fair enough.  On the other hand, to get the benefits of performance
> improvements in NCS, all you need to do is get a new NCS library and
> not get a whole new kernel from your vendor (as would likely be required
> to get any improved TCP).  My experience (as both vendor and consumer)
> has been that getting updated user-mode software to customers is typically
> much easier than getting new kernels to them.
> 
> --
>                     -- Nat Mishkin


Kernel would normally come with the machine.  However, the RPC library may
or may not come with the machine.  So, to order NCS library, I will
need to know which version/release of transports I am running.
And the vendors (you as the technology supplier, others as distributors
for different platforms) will have to keep different versions of the
library depending upon the transport available on my machine.  Unless
this chain is short and things happen smoothly, the time lag between
the day I get my machine and the day I have compatible/tuned NCS software could
be substantial - perhaps time to buy a new machine or install the new
OS and then the cycle would start all over again.
	And you as a vendor would certainly have a fun time
maintaining all different versions of software for various transports!

vipin
Disclaimer: I speak for no one but myself.

vipin@Eng.sun.com || sun!Eng!vipin