Windows Based printing opposed to web app printing? What is the diff and the deal?

[Simons]

Customer is moving from printing from a web based application . Moving to what is being called. Microsoft Windows Based printing. ................ Is this just regular printing? There is no domain and from what we hear the printers that are set up as shared are going to break. So while still using the web based software. What is happening? How is the ability to share printers being broken while requiring a Postscript " windows based printing " I hope this wasn't a dumb question. There is no domain. Several peer to peer set ups.

[rthonpm]

Love to give you some information, but what type of application is the customer using? Windows based printing in this case sounds like it's more of your standard office setup as opposed to a mainframe infrastructure, which really a web based application would be using. This is just a guess though.


--sent from my BlackBerry using the Android app

[TheOwl]

Re: Windows Based printing opposed to web app printing? What is the diff and the de

Basically, some software packages which are web based like SAP, don't use a standard print queue, they instead send RAW data directly to the machine.

Moving to a Windows based print system allows you geater control over print jobs as you can then use other third party software packages to monitor printing and stuff like that.

When you say "Windows Based Printing" you are correct in saying that it is simply a print driver on a Windows system that then prints to the printer. It may or may not be shared out to all other computers, but that is easily changed either way.