Re: RIPs:ImagePrint or Colorburst
Re: RIPs:ImagePrint or Colorburst
- Subject: Re: RIPs:ImagePrint or Colorburst
- From: Richard Wagner <email@hidden>
- Date: Mon, 16 Jun 2003 21:26:50 -0700
>
Locking up a computer to print might have been acceptable 10 years
ago,
>
but not anymore.
Roger Breton <email@hidden> wrote:
>
Well, that is entirely a function of volume, IMHO and not a function of
>
technological evolution. If you choose to operate a RIP from a
>
workstation
>
you *will* pay a performance hit as ripping is CPU intensive by
>
definition.
On this one I'll have to respectfully disagree (at least with the first
part). OS X is a complete Mach 3/BSD Unix implementation that features
preemptive & cooperative multitasking & multiprocessor/threaded process
support. The Mach kernel allocates a unique address space for each
application or process. There is no reason that one app should lock
this system. Slow down other computation-intensive tasks, fine (aka a
"performance hit"). Lock it up completely - no way. Somethin' ain't
right.
--Rich
_______________________________________________
colorsync-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/colorsync-users
Do not post admin requests to the list. They will be ignored.