Java EE create multimedia management software solution

The purpose of the new transaction model is to progressively enable end users to manage, retrieve, and manipulate stored multimedia resources-such as photos, videos, and market information-with standardized and common software. While leveraging existing in-house technology to reduce costs and generate profits, existing media services are also used to implement standardized values for multimedia resources that access them. Although there have been significant developments in storage, processing, and software over the past few years, managing digital media resources is still a very expensive thing to do. Some studies have shown that most multimedia files are unstructured resources; only a very small portion exists in relational databases and existing applications. Structured lack makes it very difficult to access and reuse digital resources effectively.

Middleware platforms--especially application servers--Always handle data resource operations. The use of application servers in creating multimedia-enhanced applications seems to be a natural extension of the inherent strength of this technology. However, the basic differences in size, structure, and metadata associated with digital resources make it necessary to operate in a different way from the relational database created by the Java EE platform and the resources that are already in use. This article explores the standards and techniques needed to create a multimedia application from both the current and developing perspectives. I will also discuss the role of Java EE in storing, indexing, accessing, and retrieving multimedia resources, with a view to extending this platform's domain to digital resources. Finally, I'll explore the problems that the Java platform must address so that users can optimize their use of multimedia resources.

Three features differentiate and define a multimedia resource. The most fundamental difference between multimedia resources and existing related data is the size of the media file. While compression technology is improving, complex video or audio streams are still used in gigabytes. Although there is now a digital content management system for storing and managing large data streams, there is no standardized application programming interface or mechanism for accessing these saved resources.

You can also differentiate multimedia resources and other data from the structure. In general, you can access and use traditional resources as separate components. However, multimedia resources may contain several elements, such as video streaming, audio streaming, related caption information, and other data sets. Maintaining this structure is a basic requirement of digital resource management system.

Finally, multimedia files are usually made up of binary information. Therefore, the traditional method of querying, indexing and retrieving files does not apply to the multimedia domain. In order for an application to successfully manage, retrieve, and manipulate a multimedia component, you must maintain the relationship between digital resources and metadata information that describes this resource feature.

Existing Java EE platform specifications, such as JDBC and JCA, illustrate protocols for data access, and you can follow these protocols to create a standard method based program to retrieve multimedia resources. The new standard must also further enhance the multimedia capabilities of the defined Java EE component model.

The way to get the best combination of multimedia and middleware platforms is how you define a storage abstraction layer for accessing digital resources. To maintain application portability, you must use or extend existing standards to address digital media storage features, such as inserting, updating, or querying resources.

Figure ⒈ defines a storage abstraction

The WebDAV specification is a protocol that extends HTTP to address the three aspects of digital media storage size, structure, and metadata (see Figure 1). It provides the ability to distribute editing and versioning across Internet protocols, and can interoperate with existing HTTP clients. WebDAV is used in networked storage solutions and Web servers, and many editing tools (including Microsoft-produced Internet Explorer browsers, Apache slide clients, Apple OS X Finder, Microsoft Office, and Adobe applications) and most of the operating systems. Many content management products that address multimedia storage support WebDAV. For example, the Apache slide system mechanism uses WebDAV as the client Access protocol. Slide provides an abstraction layer that allows the selection of mechanism types to be used for all of its storage, including content and metadata. This takes into account memory storage, database storage, xml-based storage, and so on.

The HP multimedia platform and the Apache Slide Project use the WebDAV protocol and the associated client and server application programming interfaces provided to create the digital storage abstraction functionality. This solution provides a way to use a normalized, standardized, and simple way to access multiple backend content management programs. These platforms provide Web components like the WebDAV servlet that allow developers and any WebDAV server interfaces to consolidate many WebDAV servers into a federated content server, or create custom solutions based on request information. You can use the HP WebDAV servlet and the servlet filters that can intercept WebDAV requests and perform data processing during storage and retrieval operations. Useful operations include the extraction, transformation, or indexing of metadata and content.

By leveraging the standardized Java EE component, you can create a scalable and fault-tolerant content management system based on middleware. For example, you can combine a WebDAV servlet, associated processing filters, and Apache slide to generate a content server that can store files, their metadata attributes, and the search for files based on metadata attributes. Such a system executes on the Java EE Application Architecture platform and can use features such as performance, scalability, security, and portability of the platform.

The client's memory interface can also take advantage of the two versions of J2SE and Java EE Properties and devices. Because URL settings are built into the J2SE platform, you can install a WebDAV protocol handler in the Java Virtual machine to simplify the customer interface to the WebDAV content management system. The Java EE component can potentially leverage the JCA connector implementation to create storage enterprise components and applications. For example, the WebDAV connector on the HP multimedia platform accesses a server that complies with the WebDAV protocol as an enterprise resource:

ConnectionSpec spec;
ConnectionFactory factory;
WebDAVConnection conn;
factory =(ConnectionFactory)ctx.lookup("java:comp/env/webdav/local" );
spec = new WebDAVConnectionSpec("/", "username", "password" );
conn = (WebDAVConnection)connectionFactory.getConnection
( spec );