Hi Steve,
A true UPD end to end solution with compressed EMF as the transport "protocol". Print-IT used to use PDF and still supports PDF as legacy functionality but you get the best overall performance from compressed EMF. Session printers are handled by a service on the print server that duplicates all existing queues to AD publishable UPD queues that redirect the print job to the appropriate local or remote network printer queue. Remote print servers have a service that recieves compressed streamed EMF from queues on the local print server. The print job is bit-scrambled for any WAN printing. It isn't SSL but it does use encryption keys at each end.
It's architecturally fairly similar to Thinprint but you've got the choice of print queue naming conventions and the font handling is much more efficient. It doesn't need a separate license for the print gateway component either.
ThinPrint does have embedded thinprint client devices, but back in my Citrix days when we were implementing Thinprint it usually turned out that the compression ratios you got with win32 Thinprint clients were heaps better than embedded thinprint client devices like the SEH Thinprint gateway. With win32 devices you were using compressed EMF whereas the embedded devices received a rendered compressed raw print job.
So if you want the smallest WAN print payloads you have to use win32 Thinprint clients (even Wyse embedded XP with laptop drive for spooling) anyway so I don't think not supporting embedded devices is all that much of a disadvantage for Print-IT.
By the way, Print-IT first hit the streets in 2001 so it's kind of fairly mature technology.
regards,
Rick
--
Ulrich Mack
Quest Software
Provision Networks Division
Ulrich Mack
Quest Software
Provision Networks Division
On Tue, Dec 16, 2008 at 3:06 PM, Steve Greenberg <steveg@thinclient.net> wrote:
Hi Rick,
What sort of architecture does Print IT employ?
Steve Greenberg
Thin Client Computing
34522 N. Scottsdale Rd D8453
Scottsdale, AZ 85266
(602) 432-8649
No comments:
Post a Comment