CN1224202A - Client/server printer driver system - Google Patents

Abstract

The client/server printer driver includes the ability to divide the print job into parts to be processed by the client side and the server side and to pass the server side part of the job to the client side part of the print job. The processed server subsystem to build and receive the processed server-side part of the client-side subsystem. The system has a server-side subsystem capable of receiving server-side parts from the client-side subsystem and processing the parts to create a processed server-side part and transmitting the server-side part to the client-side.

Description

Client/Server Printer Driver System

The invention relates to a printer driver. In particular, the present invention relates to a client/server system for executing print jobs on network computers ("NCs"), network appliances, and other non-PC devices capable of printing.

A network computer is a small computer connected to a local area network ("LAN") or Internet (Internet) network, containing significant local processing intelligence. Such an NC is capable of running applications downloaded from a LAN or the Internet or loaded from non-volatile local storage such as read-only CD-ROMs. NCs generally do not have local persistent memory, but store information remotely. Therefore, NC is highly dependent on the network. In addition, NC is characterized by the use of non-traditional operating systems, often uses television monitors for display and has limited local capacity. The currently planned target markets relevant to NC are:

Home - Ease of use for new consumers

Education - an inexpensive solution compared to traditional PCs with multiple controls

Commercial - cheaper connections and more control at the server/MIS level

Similarly, a network device, such as an Internet phone, is a dedicated device containing computing power and can be connected to a central server, a LAN, or the Internet.

Conventional personal computer ("PC") printer drivers are designed for use on the PC where the application program that makes the print request resides. Figure 1 shows an example driver system. The application program 130 converts the desired print data into GDI 132 or other text commands and diagrams basic data with associated page positions and/or form controls. The print job may be spooled 150 (ie, stored) to allow the user to resume work using the application 130 . Driver 100 can be used to format these commands into recognizable industry-specified data definitions (e.g., PCL) or printer driver 100 can use application 130 and/or platform intermediate commands (e.g., Microsoft Windows ^™ GDI primitives) and act on these command to create internal direct printer commands 170 to control the printer hardware 120. The printer does not necessarily have to be physically attached to the PC 110 where the application 130 and the driver 100 reside, but may be remotely located on a network such as a LAN (not shown).

One benefit of having a PC-side printer driver system is that the processing is moved to the PC itself (instead of staying at the printer), thereby allowing greater flexibility and control. Another benefit of such a system is that more advanced functions can be obtained through the use of more powerful host computers while minimizing the cost of the printer hardware itself.

As an attempt to install a conventional host-based printer driver module into a network computer module (as shown in FIG. 2), there is a problem with the consequences of the NC limitations described. The problems with current solutions in the NC environment arise from the fact that the NC devices have only a very limited amount of random access memory ("RAM") and no persistent memory (allowing them to achieve their lowest cost goals). In contrast, almost all standard PC printer drivers use local spooling to local persistent storage. For NC this is usually not possible. Also, with a small amount of local RAM, typically 4MB, there is often insufficient memory for the drivers, applications and print data, especially if color bitmaps or complex graphic images need to be printed. In addition, many NC devices being developed today have different operating systems and have different API and/or GDI interface definitions, making it very cumbersome to develop printer drivers. Therefore, legacy platform support requires the generation of new software drivers.

Traditional printing tools on the NC210 (Figure 2) use standard printing modules. For example, in the NC system, the server 200 is used to load the application program 130 , communicate with the network, and store data required by the NC 210 . NC 210 itself runs an application 130 that can request printing. Other tool details are the same as in the standard printing module for PC (see Figure 1).

The benefits of this legacy NC printing module are that 1) it is similar to the current driver module and 2) the GUI module is already known to the platform. However, the NC system has the following disadvantages of such printing modules. That is, there are severe memory and graphics constraints on the NC. Furthermore, NC hardware differences create unique problems for the software on which it runs and the hardware that interfaces with the NC. In addition, conventional spooling systems are unacceptable in situations where the NC is limited in storage space and/or memory means, and therefore cannot handle even moderately sized print jobs, especially those containing large amounts of graphics data. print job. Such a printing system cannot work with an NC with minimal RAM.

From the viewpoint of these deficiencies, the present invention proposes a new printer driver system particularly effective for NC. Briefly, the present invention divides a print job into parts that can be processed locally and parts that can be processed by the server. Typically, the server is more capable of processing data and has a larger amount of memory space than the NC. The advantage of the present invention is that the server is used for temporary storage and processing, thereby reducing the burden on the NC. Printing of more complex and high quality information is easier than using traditional drivers within the NC.

The present invention overcomes the limitations of the NC device, but still allows the user to print according to the graphics capacity currently being enjoyed. Using the present invention, the problem of lack of capacity for saving intermediate data (spooling) and lack of space for building graphic images can be overcome. The difficult task of building complex bitmaps for printing is offloaded to servers with sufficient processing power and memory. Essentially, the driver is split between the NC and the server, with each part performing the tasks most appropriate for the system it resides on. An additional job management section is added for performing the initiation of print image creation tasks on the server and managing the responses and interactions between the server and the software in the NC. Increased network traffic between NC and server when printing, but this is only a minor issue compared to the greatly enhanced capabilities provided by the present invention (especially for fast links where efficient bandwidth is placed Intranet environment in place). The present invention also provides a selectable location for drive function processing.

Additional advantages of the invention are described in part hereinafter and in part will be apparent from the description, or may be learned by practice of the invention. The advantages of the invention may be realized and attained by means of the elements and combinations particularly pointed out in the appended claims. In addition, it is to be understood that both the foregoing general description and the following detailed description are by way of example and explanation only and are not restrictive of the invention.

The block diagram of Fig. 1 shows prior art PC-based printer driver system;

The block diagram of Fig. 2 shows the conventional driver program system applied to the network computer (NC) device;

The block diagrams and process flows of Figures 3-6 relate to the printer driver system of the present invention.

The present invention can be understood more readily by reference to the following detailed description of the preferred embodiment of the invention and accompanying drawings.

Before the methods and apparatus of the present invention are disclosed and described, it is to be understood that the terminology shown and used herein is for the purpose of describing particular embodiments only and is not to be regarded as limiting. It must be noted that, as used in the specification and claims, the singular forms "a", "an" and "the" include plural referents unless the context clearly dictates otherwise.

While the present invention is particularly suited for use in conjunction with NCs, it should also be noted that the client/server printer driver system module is not limited to NCs and can be used where it may be desirable to offload the print data creation task from the requesting computer .

As pointed out above, the present invention provides a new printer driver system which can be effectively used for NC. The present invention divides print data into parts that can be processed locally and parts that can be processed by a server. The server is usually more capable of processing and has more storage space than the NC. The server is used for temporary storage and processing, thereby reducing the load of the NC.

According to the present invention, if the driver is written in a platform-independent language such as JAVA ^(R) programming language, the same driver software can be applied to any NC device that supports Java Virtual Machine (JVM) definition. The only additional requirement for this platform independence is the definition of a common API as a source of graphics and text primitives.

The present invention provides a system for processing a print job using said client/server printer driver for a client-side computing device in communication with at least one server-side computing device. The system includes a client-side driver subsystem, a server-side subsystem, and means for communicating with the client-side driver subsystem for outputting processed print jobs to signal processing means. The client-side driver subsystem itself includes a means for communicating the print job to the server-side driver subsystem of the server-side computing device. The server-side driver subsystem includes means for receiving the print job from the client-side driver subsystem delivery means. The server-side driver subsystem also includes means for processing the print job thereby to create a processed server-side print job. The server-side subsystem also includes a means for communicating the processed server-side print job to the client-side driver subsystem. Finally, said client-side driver subroutine also includes a means for receiving a processed server-side print job from said server-side subsystem.

The present invention also provides a client-server method of processing print jobs for a client-side computing device in communication with at least one server-side computing device. This method includes, but is not limited to, the step of transferring said print job from said client side to a server side computing device. The method also includes the steps of receiving at the server side the print job from the client-side transmitter and processing the print job at the server side to create a processed print job. This processed print job is then transmitted from the server side to the client side, and is received and output by the client side to the signal processing device.

For example, said signal processing means may be a printer capable of receiving and printing said print jobs. The method also includes the step of receiving and printing the print job on the printer. Additionally, the present invention provides a system for processing print jobs using a client/server print driver for a client-side computing device in communication with at least one server-side computing device. This system includes a client-side driver subsystem. This subsystem includes components for dividing the print job into one or more parts for processing by the client side, the server side, or a combination thereof. Additionally, the client-side driver subsystem includes a means for communicating the server-side portion of the print job to the server-side driver subsystem in response to the dividing means. The client-side subsystem also includes a means for processing client-side portions of the print job thereby to create one or more processed client-side print job portions. The client-side subsystem also includes means for receiving processed server-side print job portions and possibly combining their results with client-side results to create an overall result.

Additionally, the system includes a server-side driver subsystem including a means for receiving the server-side portion of said print job from said client-side driver subsystem delivery means. The server-side subsystem also includes a means for processing the server-side portion of the print job to thereby create one or more processed server-side print job portions. Finally, the server-side external subsystem includes a means for communicating one or more processed server-side print job portions to the client-side driver subsystem.

The system also includes a means for communicating with the client-side driver subsystem for outputting the processed client-side and server-side print job portions to a signal processing device, such as a printer.

The client-side portion of the print job may correspond to text information and the server-side portion of the print job may correspond to graphics information, or other arrangements based on client and server capabilities.

In addition, said dividing means may further include a means for determining the amount of communication between the client and server side computing means, and if the amount of communication is within a predetermined threshold range, said print job is divided, whereby when using One or more portions to be processed by the client side and server side or a combination thereof are preferred on the basis of minimization of communication between the client side and server side computing devices, memory capacity and processor speed, etc. In addition, the server-side computing device is a computer running on a network, which may be a local area network or the Internet.

The present invention also provides a method of processing print jobs for a client-side computing device in communication with at least one server-side computing device. The method includes but not limited to the following steps. First, the print job is divided on the client side into one or more parts to be processed by the client side, server side, or a combination thereof. Second, transmitting the server-side portion of the print job from the client-side to the server-side computing device. The client-side portion of the print job is then processed at the client-side thereby to create one or more processed client-side print job portions and receives at the server-side the print from the client-side delivery device The server-side portion of the job. Thereafter, the server-side portion of the print job is processed at the server-side, thereby creating one or more processed server-side print job portions and transmitting one or more processed server-side print job portions at the server-side to the client-side The server-side print job portion of the process. Finally, the processed server-side print job parts are received at the client side and the processed client-side and server-side print job parts are output to a signal processing device (eg a printer).

The signal processing means may be a printer capable of receiving client-side and server-side print jobs and printing the print jobs. The client-side portion of the print job may correspond to text information and the server-side portion of the print job may correspond to graphics information, or other logical arrangement or division of tasks. Additionally, the client-side and server-side parts may relate to "low"/"medium" and "high" quality parts, respectively. As shown in the example below, there can be multiple client-side or server-side parts, so, by way of example only, the "low" and "medium" quality parts should be processed separately locally, see e.g. Figure 6 .

In addition, said dividing step further includes determining the amount of communication between said client and server side computing devices, if said amount is within a predetermined threshold range, based on minimizing the amount of communication between the client and server side computing devices, Processing speed, RAMH and permanent buffer storage etc. Divide the print job such that one or more parts are processed by client side, server side or a combination thereof is preferred.

The following example attempts to provide a complete disclosure to those skilled in the art, and describes how to construct, use and evaluate the system, as a pure example of the present invention rather than as a list of the scope of the inventor's invention of the present invention limit. Attempts are made to ensure accuracy with respect to quantities (eg, amounts stated, etc.), but some errors and deviations may occur.

example

example 1:

In one embodiment, the client/server printing module operates as follows (in the context of the NC) (see Figure 3). The following functions are handled by the server 300: 1) application service, communication and data storage; 2) print job spooling 350; and 3) print data creation 360. The following functions are handled by NC 310: 1) execution of application programs 330 requesting printing; 2) job management and user interface ("JMUI") control 380; 3) printer user interface 340; and 4) print formatting 370. A printer device 320 is typically connected to NC 310 as shown. However, network printing is readily available using the system of the present invention by simply redirecting the formatted print data 370 to the appropriate communication channel and output device.

The server 300 provides and runs the application program 330 executable by the NC 310 upon request from the NC 310 . NC 310 running application program 330 generates a print request. This request is provided locally to NC 310 and job management and user interface control subsystem 380 . This subsystem 380 is part of the printer driver 100 . The JMUI subsystem 380 understands the printer user interface 340 and provides a user interface to users of the system. Subsystem 380 transmits the print request to server 300 via a network (not shown). On the server 300 side, the print request is spooled 350 and the print data (typically a bit image) 360 is created away from the NC 310 . Finally, the print data is returned from the server 300 to the NC 310, where final print formatting 370 is performed. A printing device 320 that is local to (or network attached to) the NC 310 receives the formatted data and prints the job.

Obviously, this system no longer requires the NC to provide local memory and storage space for spooling print jobs. The system also relieves the NC from having to allocate processing and memory resources to create the actual print data.

Example II:

In another embodiment (FIG. 4), the present invention provides a client/server printing system for NC. In this model, print data is characterized by the NC410 portion of the print driver 100 and only those that require complex, The remotely processed print job portion is transmitted to the server 400 . Therefore, simple print data creation tasks are handled locally. This system provides efficient local processing of those parts of the print job that do not overload the NC. In this case, the job part can be done between the NC and the server on a "per page", "per frequency band", "per row", "per job" or other basis depending on available resources segmentation. With the NC client/server print driver model described above, complex parts of the print job are handled remotely. This assignment is not absolute when describing the system in terms of simple and complex print jobs. For example, the division of labor criteria can be based on available memory (RAM), persistent memory, page orientation, and the like.

In particular, the system was run as described in Example I, with the following changes. First, the JMUI control subsystem 480 attempts to provide an additional functionality. Specifically, the JMUI subsystem 480 is now able to determine whether the application print job is relatively simple (eg, text with small memory requirements) or complex (eg, graphics with large memory requirements). The JMUI subsystem 480 transmits the complex part to the server 400 for spooling 450 print data build 460 . JMUI subsystem 480 keeps the simple part at NC 410 for local print data build 465 . Finally, print formatting 470 is under the control of JMUI subsystem 480, thereby enabling JMUI subsystem 480 to monitor the necessary status and page position information 482 to ensure that the final printer 420 output representation comes from the server 400 and NC 410 ( Complete page data of the data part processed on the client) side. Thus, the JMUI 482 is responsible for reconstructing the print data before passing the command to the printing device 420 itself. In this example, only the complex part is transmitted to server 400 and spooled 450 and processed 460 there.

Example III:

Also, in another example ( FIG. 5 ), all print jobs from NC 510 application 530 are sent directly to server 500 for spooling 550 . In this embodiment, the JMUI subsystem 580 then receives the spooled job from the server 500, determines the complexity level 585, and assigns the print data build based on that determination (560 or 565). For simple print jobs, the data is built 565 locally, however, for complex print jobs, the server 500 print data build system 560 in turn references 552 the spooled print job 550 (again on the server 500 side) and uses It creates print data 560 corresponding to complex data including print lines 562 or other data. The rest of the system is the same as above.

Example IV:

Additionally, in other examples, the present invention provides a client/server print driver system adapted to operate with an NC. This embodiment is shown substantially in FIG. 6 .

For the global Internet, the additional traffic from NC print requests is a hindrance since every print decoding needs to go in and out of the Internet. As an enhancement to the previous examples, the following examples are provided which return some basic (text and simple data block graphics) driver image functionality to the NC610. Standard printing is performed locally, does not require LAN or Internet communication, and can therefore be very fast. On the other hand, the server 600 contains a part of the driver 100 which is used to create complex graphic images.

The server 600 loads the application program 630 into the NC 610 . An NC 610 application 630 wishing to print creates a print object (eg, a GDI command) targeting a particular locally attached printer 620 or a remote printer (not shown). The driver 100 fetches the data and determines how to build the print image and presents the user interface 640 to the customer based on the type of data. In order to minimize the impact of network delays during the printing process, the storage of simple objects (text, data block graphics) and the creation of print data are performed 665 locally, but since the server 600 has sufficient persistent memory and processing power to handle large amounts of data , therefore, the storage and establishment of the relatively complex graph 660 is performed at the server 600 . It may even be feasible for smart applications to pass pointers or indices to complex bitmaps and other graphics that may be stored in spooled data 650 to the driver, rather than all the data. Application data can be sent to the spooler 650 or local NC based on the complexity of the data so that complex large data blocks are never downloaded to the NC until they are formatted for printing . The driver part of the present embodiment will be explained in detail below.

Once data is received for printing, the data is often stored 650 (spooled at server 600) to allow the user to return to the application 630 relatively quickly (this step can be omitted if the amount of data is very small). The job management portion 680 of the driver selects the portion of data to be printed, usually a portion of the page identified by a number of print lines called bands. This part identifies what kind of printing objects are located in this printing zone, and then the server 600 manages the creation of print image data related to this zone, selects partial image creation for simple text or initiates the creation of complex graphic data . Server 600 responds with graphic image data associated with the requested print tape. This graphics data 668 is then combined with any locally developed text or other data (from 665) to create print strip data 670. This print strip data is corrected with the print formatter 670 for printer mechanical, electrical characteristics (wiring, spacing, timing), etc. It is then sent to the printer device 620 .

By splitting the driver image development between the NC and the server, very simple, relatively inexpensive printers can print complex graphics desired by the user that cannot be printed with the limited processing power of the NC device. Plus, simple printing is not limited or delayed by Internet latency.

Referring to FIG. 6, a server 600 is used to store document data, NC application programs, NC printer driver software, print spoolers, and standard image/font ("I/F") technology. The server 600 computer can generate the appropriate print data and can transmit the print image to a remote printer or a printer local to the NC610. NC 610 is responsible for running applications requiring file data, requesting loading of appropriate print drivers, JMUI control 682 (including printer user interface 640), determining print quality, passing said print job data to the appropriate local NC I/F technology (usually from the application itself or from an enhanced local interface) or to said server for its I/F technology and, if required, performs the build-up of partial print data and reorganizes the client-side and The server side prints part of the data and outputs to the printer device 620 attached to the NC 610 (or uploads the created print data to the server 600, network or other devices for remote printing or processing).

The client/server print driver system operates as follows. The document data 605 is loaded from the server 600 to the NC 610 or generated by the user by using the client side operation application 630 . This application software 630 itself can be downloaded 607 from the server 600 as a standard feature of NC systems. Then, the NC 610 runs the application program 630 to access the document data 605 . When the user of the application program 630 requests to print the document data 605 , the application program 630 transfers the document data 605 to the NC-side printer driver loading module 632 . This module 632 determines which type of driver is loaded 634 and then requests the server 600 to transmit the appropriate driver software 634 to the client 610. This driver software 634 is used to manage the remainder of the print process.

In one embodiment, the server 600 and client 610 print driver 100 subsystem can obtain document data 605 in the application. Accordingly, document data 605 is automatically transferred to spooler 650 on server 600 in one embodiment upon the application 630 issuing a print request. Additionally, this transmission can only take place if the server portion of the printing device is activated.

Once the driver software 634 is loaded, the JMUI subsystem 680 of the printer driver software is activated. The JMUI subsystem 680 is integrated with the printer user interface 640 and performs a series of functions. First, the JMUI subsystem 680 determines whether the file data 605 requires "high", "medium" or "low" quality (complexity) processing 685 . One skilled in the art should recognize that the determination of "high", "medium" or "low" quality is arbitrary and that further and different differences. Other criteria may also be used to separate the print jobs between client and server, including size, complexity, data type, and the like. The JMUI subsystem 680 is capable of monitoring server-side processing tasks as well as NC local printing tasks 672 . Finally, the JMUI subsystem 680 can indicate to the server 600 whether to print to the NC local printer device 664 or the remote printer device 662 .

After the driver determines the print quality 685, the JMUI subsystem 680 passes the document data to the appropriate image/font (I/F) subsystem (652, 654, 656 or 658). The I/F subsystem decodes text and graphics data into locations on the page as a bit image raster. In one embodiment, possible I/F subsystems include, but are not limited to: 1) application I/F technology 658, 2) enhanced NC native I/F technology 656, 3) enhanced server-side I/F technology, 4) standard server side I/F technology. For example, “low” quality jobs are handled by application I/F technology 658 , while “medium” quality jobs are handled by enhanced NC native I/F technology 656 . Finally, "high" quality jobs can refer to standard server-side I/F technology 652 . In addition, JMUI subsystem 680 may further determine that some or all of any job is processed on server 600 by enhanced server-side I/F technology 654 . In either event, the appropriate I/F subsystem is responsible for the setup of the print data on its input. Additionally, Low, Medium, and High quality can be determined depending on the type of driver.

On the server 600 side, document data is extracted from the spooler 650 . On the NC 610 or client side, the document data is loaded using the I/F subsystem ( 650 or 658 ) directly from the application 630 . Various I/F subsystems are responsible for the establishment of print data. NC 610 is responsible for reassembling client-side and server-side print data 670 from the I/F subsystem and formatting it for output to printing device 620 . However, when the JMUI subsystem 680 indicates that remote printing 662 is desired, the server-created print data 660 is transmitted to the server 600 where the final print data is transmitted to the appropriate remote printer (not shown).

This embodiment provides server power for print spooling and allows processing at higher quality than the entire local NC system. Additionally, LAN traffic (from the NC to the server) is greatly reduced by allowing local processing of text and simple images. However, these embodiments are also capable of high quality (complex) printing if needed or desired at the expense of increased LAN traffic.

It will be apparent to those skilled in the art that various modifications and changes can be made without departing from the spirit and scope of the invention. Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. Therefore, the foregoing description and examples are given by way of illustration only, with the true scope and spirit of the invention indicated by the following claims.

Claims (30)

1. A system for processing print jobs utilizing a client/server printer driver for a client-side computing device in communication with at least one server-side computing device, the system comprising: (a) a client-side driver subsystem including means for communicating said print job to a server-side driver subsystem of a server-side computing device; (b) Server-side driver subsystem, including: (i) means for receiving said print job from the client-side driver subsystem delivery means; (ii) means for processing said print job to thereby create a processed server-side print job; (iii) means for communicating said processed server-side print job to said client-side driver subsystem; Wherein, the client-side driver subsystem further includes a means for receiving a processed server-side print job from the server-side subsystem, (c) means in communication with the client-side driver subsystem for outputting the processed print job to the signal processing means. 2. The system of claim 1, wherein said signal processing means includes a printer capable of receiving and printing said print job. 3. The system of claim 1, wherein said client computing device is a network computer. 4. The system of claim 1, wherein said server-side computing device is a computer operating on a network. 5. The system of claim 4, wherein said network is a local area network. 6. The system of claim 4, wherein the network is the Internet. 7. A system for processing print jobs using a client/server printer driver for a client-side computing device in communication with at least one server-side computing device, the system comprising: (a) The client-side driver subsystem includes: (i) a means for dividing said print job into one or more portions for processing by the client side, the server side, or a combination thereof; (ii) means for communicating, in response to said dividing means, said server-side portion of said print job to said server-side computing means; (iii) means for processing client-side portions of said print job to thereby create one or more processed client-side print job portions; (iv) means for receiving the processed server-side portion; (b) The server-side driver subsystem includes: (i) means for receiving said server-side portion of said print job from said client-side driver subsystem delivery means; (ii) means for processing server-side portions of said print job thereby to create one or more processed server-side print job portions; and (iii) means for communicating said one or more processed print job portions to said client-side driver subsystem; and (c) means in communication with said client-side driver subsystem for outputting the processed client-side and server-side print job portions to a signal processing device. 8. The system according to claim 7, wherein said signal processing means comprises a printer capable of receiving said client-side and server-side print jobs and capable of printing said print jobs. 9. The system of claim 7, wherein said client computing device is a network computer. 10. The system of claim 7, wherein the client-side portion of the print job corresponds to text information. 11. The system of claim 7, wherein the server-side portion of the print job corresponds to the graphics information. 12. The system of claim 7, wherein said server-side computing device is a computer operating on a network. 13. The system according to claim 7, wherein said dividing means further comprises a means for determining the amount of communication between the client-side and server-side computing means, and if said amount is within a predetermined threshold range, dividing said printing A job whereby one or more portions to be processed by the client side, the server side, or combinations thereof are prioritized based on minimizing the amount of communication between the client side and server side computing devices. 14. The system of claim 13, wherein said network is a local area network. 15. The system of claim 13, wherein the network is the Internet. 16. A method for processing a print job for a client-side computing device in communication with at least one server-side computing device, the method comprising the steps of: (a) transferring said print job from said client side to said server side computing device; (b) receiving said print job from said client-side delivery device at a server side; (c) processing said print job at the server side to create a processed print job; (d) transmitting said processed print job at the server side to said client side; (e) receiving said processed print job at the client side; and (f) outputting said processed print job to a signal processing device. 17. The method according to claim 16, wherein said signal processing means comprises a printer capable of receiving and printing said print job, said method further comprising receiving said print job and printing said print job on said printer step. 18. The method of claim 16, wherein said client computing device is a network computer. 19. The method of claim 16, wherein said server-side computing device is a computer operating on a network. 20. The method of claim 19, wherein said network is a local area network. twenty one. The method of claim 19, wherein the network is the Internet. twenty two. A client/server method for processing print jobs for a client-side computing device in communication with at least one server-side computing device, the method comprising the steps of: (a) dividing the print job at the client side into one or more portions to be processed at the client side, at the server side, or a combination thereof; (b) transferring the server-side portion of the print job from the client-side to the server-side computing device; (c) processing client-side portions of the print job at the client-side thereby to create one or more processed client-side print job portions; (d) receiving at the server side a server-side portion of said print job from said client-side delivery device; (e) processing server-side portions of the print job at the server-side thereby to create one or more processed server-side print job portions; (f) transmitting one or more processed server-side print job portions at the server side to the client side; (g) receiving said processed server-side print job portion at the client side; and (h) Outputting the processed client-side and server-side print job portions to a signal processing device. twenty three. The method according to claim 22, wherein said signal processing means comprises a printer capable of receiving client-side and server-side print job parts and printing said print job. twenty four. The method of claim 22, wherein said client-side computing device is a network computing device. 25． The method of claim 22, wherein the client-side portion of the print job corresponds to the text portion. 26． The method of claim 22, wherein the server-side portion of the print job corresponds to the graphics portion. 27． The method of claim 22, wherein said server-side computing device is a computer operating on a network. 28． The method according to claim 22, wherein said dividing step further comprises the step of determining the amount of communication between the client-side and server-side computing devices, and dividing said print job if said amount is within a predetermined threshold range, by This is preferred on the basis of minimizing the amount of communication between the client-side and server-side computing devices so that one or more portions are processed by the client-side, server-side, or a combination thereof. 29． The method of claim 27, wherein said network is a local area network. 30． The method of claim 27, wherein said network is said Internet.

Images