1. Field of the Invention
This invention relates to a printer or printer system using the Java language to control rasterizing an image and to control printing.
2. Description of the Background
The Internet is undergoing explosive growth and many new technologies are being developed to keep up with this growth. Previously, in order to develop applications quickly, application developers sought to use specialized cross-platform application development techniques which create applications for multiple hardware and software platforms. For example, operating systems (i.e. Solaris, Windows 95, Windows 3.x, OS/2 and Unix) create applications and executable files differently and have been implemented on various processor types (Intel processors, 680.times.0, Power PCs, and Sun SPARCS). To develop applications for all permutations of operating systems and hardware is difficult and extends the product development cycle. To make cross-platform development faster and easier, Sun Microsystems developed a language called Java which is object-oriented but simple. Java is described in Java in a Nutshell: A Desktop Quick Reference for Java Programmers by David Flannagan, published by O'Reilly & Associates, Inc., as well as in the Sun Series of books published by Prentice Hall Books entitled Core Java, Instant Java, Java by Example, and Just Java by Cornell, Pew, Jackson and Van Der Linden, respectively, which are incorporated herein by reference. One of Java's advantages is that it is a portable language which is independent of operating systems and hardware architectures. Further, applications developed using Java are adaptable or extendable using Java's ability to download new classes dynamically and to add the downloaded classes to an existing class hierarchy. Java also provides the advantages of distribution, language interpretation, security, high performance and a multi-threaded implementation.
Java enables applications to be written using an extensible set of objects, with each set of objects being defined in a separate group of objects called a package. The core set of objects for Java are defined in the java.lang package and describe the most central characteristics of the Java language. One of Java's advantages is that the character type that Java uses is the Unicode standard which allows English and Asian characters to be represented consistently and together in applications or documents generated using Java.
Other languages have been used to represent the layout of documents as they appear on printers. PostScript by Adobe is an extendable page-layout language which supports text and graphics on the same page. Some aspects of PostScript are described in PostScript by Example by Henry McGilton and Mary Campione, published by Addison-Wesley Publishing Company, the contents of which are incorporated herein by reference. PostScript uses stacks and dictionaries to extend the language. Some PostScript printers also have been equipped with non-volatile memories which are used to store configuration information for the printers. However, PostScript's lack of strong security features has enabled malicious users of the printer to update the parameters stored in the non-volatile memory, thereby disturbing the printer's use in network environments.
Other printer languages, such as PCL by Hewlett-Packard, have evolved from uni-directional, dot-matrix line printers and therefore lack many of the operators needed to control the placement of images on a page. PCL also lacks modularity. The macros defined by PCL use globally scoped variables that can affect the performance of other macros defined by the language.
Currently, all of the applications that print from host systems have to convert their internal document format to PostScript or PCL and then download the document to the printer using a printer driver designed to work with the specifics of the connected printer. Since there is a wide variety of printers that can be used, each with a slightly different set of features and/or bugs, a large number of printer drivers have traditionally been shipped with applications, even though end-users actually only need the printer drivers for their specific printers. Furthermore, using conventional printing techniques, an inadvertent change in the printer driver used could cause the printer to print out the commands which describe how a page is to be laid out rather than interpreting the commands and rendering a resulting image. Further, for printers which support downloadable fonts, downloading of fonts often has been restricted to downloading to the printer's RAM, ROM font cartridge or attached hard disk.
This model of application and printer driver interaction has created an increase in work performed by end-users because of the inflexibility and limited communication capability of the printer when communicating with the application.
It is an object of the present invention to overcome at least one of the deficiencies described above in the implementation of a printer language.
It is a further object of the present invention to provide a printer which uses the Java language to interpret page-layout requests.
It is another object of the present invention to provide bi-directional communication between an application or printer driver and a Java printer to enable a user to define how a page or series of pages should be laid out.
It is yet another object of the present invention to provide a World Wide Web interface to control a Java printer of the present application.
It is a further object of the present invention to use the Java-specific features of object-orientation, distribution, interpretation, security, architecture and neutrality, portability, performance, multi-threadedness, and dynamic loading to implement an improved printer.
A more complete appreciation of the invention and many of the attendant advantages thereof will be readily obtained as the same becomes better understood by reference to the following detailed description when considered in connection with the accompanying drawings, wherein:
Referring now to the drawings, wherein like reference numerals designate identical or corresponding parts throughout the several views,
In the first embodiment, Java print requests are received by the print server 102 via the external communication link 104 through a socket listening on a designated port (i.e., port 80 for hypertext transfer protocol), and the print server 102 converts the received print request from a Java request to a printer request for the attached laser printer 100 in the printer language of the attached laser printer 100. The print server 102 also can receive standard hypertext transfer protocol (HTTP) requests and produce World Wide Web (WWW) pages as a result or update the configuration of the laser printer 100 if the HTTP request has been sent by a system administrator or an authorized user.
As shown in
Java has a rich set of graphics operators that match PostScript and PCL, and since Java is an object-oriented language which provides extensions, new complex graphics operators can be created which are subclasses of the existing graphics primitives, thereby allowing complex images to be described compactly. The present invention extends the Graphics class of the java.awt package to control drawing of images on pages, by implementing a new class, Printer. Each of the other methods of the Graphics class would likewise be implemented to allow colors and fonts to be changed and to allow lines and filled and empty polygons to be drawn. For example, calling java.awt.Printer.drawString(msg, x, y) would cause the string “msg” to be drawn on a page at position (x,y). The Printer class also would implement a function, similar to PostScript's “showpage” command, which signals that a complete page has been rendered and that the resulting image should be transferred to Java laser printer 110. Further, based on the built-in security, network capability and multi-lingual support of Java, a Java printer can handle inputs from different platforms in multiple languages and create the desired documents.
As shown in
When the Java printer 110 which was listening on the appropriate port receives the request for this document, the Java printer 110 would parse the name of the document requested from the rest of the request and determine that the system administrator wished to configure the printer for a particular user. (The complete specification for the format of an HTTP request or response can be found in the HTTP. standard (versions 1.1 or 1.0). Information on HTML can be found in Using HTML: The Definitive Guide by Musciano and Kennedy, and information on Internet information services can be found in Managing Internet Information Services by Liu et al. The contents of these references are incorporated herein by reference.) In response to a request for a document, the Java printer 110 would send back to the browser, via the socket used to send the request, a response like the page shown in
Additional values can be set, as shown in the
Further, the Java printer 110, or the combination print server 102 and laser printer 100, can utilize the external communication link 104 dynamically to retrieve documents or portions of documents from other web sites for printing or for otherwise modifying the operation of the Java printer 110, such as loading updates to printer code. The Java printer 110 can likewise use the external communication link 104 for downloading fonts from remote locations whenever the font is needed. To download fonts, changes, or other information, the Java printer 110 can use any transfer protocol implemented by an included Java package, including HTTP, FTP, Gopher, etc. By specifying the URL from which the information should be obtained and using the java.net.getcontent( ) method information can be received as a String. In addition, for new or previously unimplemented protocols, a java.net.URLConnection object would be used to receive and parse the contents of a new document type. As described earlier, this provides an advantage over PostScript printers which have to have fonts loaded in their RAM, ROM or hard disk in order to use them. Table 1 below shows some of the advantages of using Java over HP/PCL and PostScript.
As shown in
Since Java is multi-threaded, the Java printer 110 can multi-task between any of its functions (i.e., printing the current job, receiving a new job, pausing a job, killing a job, reordering the job such that a job is made the next job to be printed or the last job to be printed, displaying characteristics of a job, resuming a paused job, setting default configuration information or determining the status of the printer). Conventional printers perform one job at a time and do not have such a printing capability.
As shown in
As shown in
As shown in
As shown in
Furthermore, to smooth the transition from PostScript and PCL to Java, Java printers can be implemented which utilize subclasses of the Printer class that receive and render PostScript, PCL or both. These classes can even be added dynamically by the system administrator when they become available. The new classes would be loaded using a URL specified by the system administrator. On the other hand, traditional printer drivers which utilize GDI calls can be modified to generate Java code from the received GDI. application. For example, since windows documents are generated using standard GDI calls, a Java printer 110 can be selected like any other supported printer, and the Java printer driver then would convert the Windows GDI calls into Java code to be sent to the Java printer 110.
Obviously, numerous modifications and variations of the present invention are possible in light of the above teachings without departing from the intended scope of the present invention. Such changes include storing the user profile information in remote databases rather than in the Java printer 110 itself. By using the Java SQL API, also known as the JDBC, remote databases can store the user profile information, and applets still can query and update the user profile information. Since the JDBC specification has not been finalized, the version 0.70 draft specification dated May 7, 1996 is incorporated herein by reference.
This application is a continuation of and is based upon and claims the benefit of priority under 35 U.S.C. §120 for U.S. Ser. No. 10/684,429 (now U.S. Pat. No. 7,755,785), filed Oct. 15, 2003, which is a divisional of U.S. Ser. No. 10/625,509 (now U.S. Pat. No. 7,508,533), filed Jul. 24, 2003, which is a divisional of U.S. Ser. No. 08/856,183 (now U.S. Pat. No. 6,628,413), filed May 14, 1997, which claims the benefit of priority to provisional U.S. Ser. No. 60/017,398, filed May 14, 1996 the entire contents of which all of these applications are incorporated herein by reference in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
4642792 | Clements et al. | Feb 1987 | A |
5075874 | Steeves et al. | Dec 1991 | A |
5121113 | Kedge et al. | Jun 1992 | A |
5165014 | Vassar | Nov 1992 | A |
5228118 | Sasaki | Jul 1993 | A |
5293466 | Bringmann | Mar 1994 | A |
5323393 | Barrett et al. | Jun 1994 | A |
5371837 | Kimber | Dec 1994 | A |
5455599 | Cabral et al. | Oct 1995 | A |
5469373 | Kashiwazaki et al. | Nov 1995 | A |
5488223 | Austin et al. | Jan 1996 | A |
5495561 | Holt | Feb 1996 | A |
5537626 | Kraslavsky et al. | Jul 1996 | A |
5566278 | Patel et al. | Oct 1996 | A |
5638497 | Kimber et al. | Jun 1997 | A |
5699494 | Colbert et al. | Dec 1997 | A |
5784553 | Kolawa et al. | Jul 1998 | A |
5784622 | Kalwitz et al. | Jul 1998 | A |
5790855 | Faustine | Aug 1998 | A |
5828840 | Cowan et al. | Oct 1998 | A |
5956487 | Venkatraman et al. | Sep 1999 | A |
6003065 | Yan et al. | Dec 1999 | A |
6139177 | Venkatraman et al. | Oct 2000 | A |
6170007 | Venkatraman et al. | Jan 2001 | B1 |
6314521 | Debry | Nov 2001 | B1 |
6321266 | Yokomizo et al. | Nov 2001 | B1 |
6628413 | Lee | Sep 2003 | B1 |
7508533 | Lee | Mar 2009 | B2 |
20020078160 | Kemp et al. | Jun 2002 | A1 |
20030043272 | Nagao et al. | Mar 2003 | A1 |
Number | Date | Country |
---|---|---|
64-008080 | Jan 1989 | JP |
01-204768 | Aug 1989 | JP |
03-237525 | Oct 1991 | JP |
03-262674 | Nov 1991 | JP |
04-231604 | Aug 1992 | JP |
05-122424 | May 1993 | JP |
05-198926 | Aug 1993 | JP |
05-221090 | Aug 1993 | JP |
06-187334 | Jul 1994 | JP |
06-243081 | Sep 1994 | JP |
06-348436 | Dec 1994 | JP |
08-065982 | Mar 1996 | JP |
08-071799 | Mar 1996 | JP |
08-077650 | Mar 1996 | JP |
08-078023 | Mar 1996 | JP |
08-090846 | Apr 1996 | JP |
08-115180 | May 1996 | JP |
08-175067 | Jul 1996 | JP |
08-309020 | Nov 1996 | JP |
08-337185 | Dec 1996 | JP |
09-077166 | Mar 1997 | JP |
09-087010 | Mar 1997 | JP |
09-223096 | Aug 1997 | JP |
09-0230537 | Sep 1997 | JP |
09-280373 | Oct 1997 | JP |
09-284515 | Oct 1997 | JP |
WO 9601456 | Jan 1996 | WO |
Number | Date | Country | |
---|---|---|---|
20100208302 A1 | Aug 2010 | US |
Number | Date | Country | |
---|---|---|---|
60017398 | May 1996 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 10625509 | Jul 2003 | US |
Child | 10684429 | US | |
Parent | 08856183 | May 1997 | US |
Child | 10625509 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 10684429 | Oct 2003 | US |
Child | 12768026 | US |