This document explains in details how to setup a derby database connection using Hibernate and caching. This document assumes you are using Red5 0.8 and the latest Hibernate Release 3.3.1.
This update requires very latest Red5 svn trunk
The demo application is built using the Red5Plugin, simply import the project into eclipse.
http://www.hibernate.org/ DAO takes a similar approach to the Spring DAO JDBC setup but adds first and second level caching and example is described here docs:Red5 and Spring JDBC Hibernate.
Required Libraries
* aspectjweaver.jar - Found in Spring with dependancies distribution.
* c3p0-0.9.1.2.jar
* dom4j-1.6.1.jar - Hibernate dependancy, found in distribution
* javassist-3.4.GA.jar - Hibernate dependancy, found in distribution
* antlr-3.1.1.jar - Hibernate dependancy, found in distribution. Already included with Red5.
* commons-collections-3.2.1.jar - Hibernate dependancy, found in distribution. Already included with Red5.
* jta-1.1.jar - Hibernate dependancy, found in distribution. Already included with Red5.
* slf4j-api-1.5.2.jar - Hibernate dependancy, found in distribution. Already included with Red5.
* ehcache-1.6.0-beta1.jar - The latest ehcache which removes backport concurrent dependancy.
* jsr107cache-1.0.jar - EHCache 1.6 dependancy.
* derby-10.4.2.0.jar
* hibernate3.jar - Get the latest which is 3.3.1.
* spring-aop-2.5.5.jar - Already included with Red5.
* spring-orm Read more about: Red5 and Hibernate
Will tell the application to start the stream on application startup, which will make it act like a real web tv stream. Otherwise the stream will startup on client connection.
Sets up page / swf url checks for playback security, publish names for publish security, and shared object names and checks for shared object security.
Playback Security Bean
Supply text files with domain entries seperated by a new line.
Ad serving describes the technology and service that places advertisements on web sites. Ad serving technology companies provide software to web sites and advertisers to serve ads, count them, choose the ads that will make the website or advertiser most money, and monitor progress of different advertising campaigns.
An ad server is a computer server, specifically a web server, that stores advertisements used in online marketing and delivers them to website visitors.
The content of the webserver is constantly updated so that the website or webpage on which the ads are displayed contains new advertisements -- e.g., banners (static images/animations) or text -- when the site or page is visited or refreshed by a user.
In addition, the adserver also performs various other tasks like counting the number of impressions/clicks for an ad campaign and report generation, which helps in determining the ROI for an advertiser on a particular website.
Ad servers come in two flavors: local ad servers and third-party or remote ad servers. Local ad servers are typically run by a single publisher and serve ads to that publisher's domains, allowing fine-grained creative, formatting, and content control by that publisher. Remote ad servers can serve ads across domains owned by multiple publishers. They deliver the ads from one central source so that advertisers and publishers can track the distribution of their online advertisements, and have one location for controlling the rotation and distribution of their advertisements across the web.
The local ad server was first developed and introduced by NetGravity in January 1996 for delivering online advertising at major publishing sites such as Yahoo and Pathfinder. The company was founded by Tom Shields and John Danner, and based in San Mateo, California. In 1998, the company went public on NASDAQ (NETG), and was purchased by DoubleClick in 1999. Read more about: Ad serving
