util

1.	6.0 JDK Core
2.	6.0 JDK Modules
3.	6.0 JDK Modules com.sun
4.	6.0 JDK Modules com.sun.java
5.	6.0 JDK Modules sun
6.	6.0 JDK Platform
7.	Ajax
8.	Apache Harmony Java SE
9.	Aspect oriented
10.	Authentication Authorization
11.	Blogger System
12.	Build
13.	Byte Code
14.	Cache
15.	Chart
16.	Chat
17.	Code Analyzer
18.	Collaboration
19.	Content Management System
20.	Database Client
21.	Database DBMS
22.	Database JDBC Connection Pool
23.	Database ORM
24.	Development
25.	EJB Server
26.	ERP CRM Financial
27.	ESB
28.	Forum
29.	Game
30.	GIS
31.	Graphic 3D
32.	Graphic Library
33.	Groupware
34.	HTML Parser
35.	IDE
36.	IDE Eclipse
37.	IDE Netbeans
38.	Installer
39.	Internationalization Localization
40.	Inversion of Control
41.	Issue Tracking
42.	J2EE
43.	J2ME
44.	JBoss
45.	JMS
46.	JMX
47.	Library
48.	Mail Clients
49.	Music
50.	Natural Language Processing
51.	Net
52.	Parser
53.	PDF
54.	Portal
55.	Profiler
56.	Project Management
57.	Report
58.	RSS RDF
59.	Rule Engine
60.	Science
61.	Scripting
62.	Search Engine
63.	Security
64.	Sevlet Container
65.	Source Control
66.	Swing Library
67.	Template Engine
68.	Test Coverage
69.	Testing
70.	UML
71.	Web Crawler
72.	Web Framework
73.	Web Mail
74.	Web Server
75.	Web Services
76.	Web Services apache cxf 2.2.6
77.	Web Services AXIS2
78.	Wiki Engine
79.	Workflow Engines
80.	XML
81.	XML UI

Java Source Code / Java Documentation » 6.0 JDK Modules com.sun.java » util

OpenJDK:
License:	The GNU General Public License (GPL)
URL:	https://openjdk.dev.java.net
Description:

Package Name Comment

com.sun.java.util.jar.pack

This package provides methods to read files from a JAR file and to transform them to a more compact transfer format called Pack200. It also provides methods to receive the transmitted data and expand it into a JAR file equivalent to the original JAR file.

The pack methods may be used by application developers who wish to deploy large JARs on the web. The unpack methods may be used by deployment applications such as Java Web Start and Java Plugin.

In typical use, the packed output should be further compressed using a suitable tool such as gzip or java.util.zip.GZIPOutputStream. The resulting file (with a suffix ".pack.gz") should be hosted on a HTTP/1.1 compliant server, which will be capable of handling "Accept-Encoding", as specified by the HTTP 1.1 RFC2616 specification.

NOTE: It is recommended that the original ".jar" file be hosted in addition to the ".pack.gz" file, so that older client implementations will continue to work reliably. (On-demand compression by the server is not recommended.)

When a client application requests a ".jar" file (call it "Large.jar"), the client will transmit the headers "Content-Type=application/x-java-archive" as well as "Accept-Encoding=pack200-gzip". This indicates to the server that the client application desires an version of the file encoded with Pack200 and further compressed with gzip.

The server implementation will typically check for the existence of "Large.pack.gz". If that file is available, the server will transmit it with the headers "Content-Encoding=pack200-gzip" and "Content-Type=application/x-java-archive".

If the ".pack.gz" file, is not available, then the server will transmit the original ".jar" with "Content-Encoding=null" and "Content-Type=application/x-java-archive".

A MIME type of "application/x-java-pack200" may be specified by the client application to indicate a ".pack" file is required. However, this has limited capability, and is not recommended.

Package Specification

Network Transfer Format Specification : http://jcp.org/en/jsr/detail?id=200

util

Package Specification

Related Documentation