A online audio recording and sharing utility application that demonstrates the power of Red5 with Adobe Flash client.
- January 31, 2010
- Red5
Red5 to mysql without JDBC
In this tutorial we see how to connect to a mysql database, regardless of whether you have access to JDBC adapter on your Red5 running server. Definitely JDBC would be faster, but this method will get you across just fine in any Red5 project involving databases.
Since we wont be using Java way of connecting to mysql, i pick php as the delegate for that. so our communication will be like this:
JAVA -> PHP -> MYSQL
and
MYSQL -> PHP -> JAVA
(more…)
- December 16, 2009
- General
Flash fever on mobile devices
Here is this cool video where you can see how Adobe Flash is fast capturing millions of hearts. Its pretty obvious that in a few years we will have flash all around us in many forms. The ability of the flash team to have put flash out there as a choice for iphone one way or the other shows their determination and firm belief in what thy are trying to do. Watch this and give yourself a treat on the penetration of flash technology.
Handling application stop event in tomcat based red5 compilations
As you would know red5 is a media server package, which runs on top or other server cores like Tomcat and Jetty. There are few minor differences , hence in the way both compilations handle events and behaviors. The one we will be talking about here is specifically the “appStop” event. The “appStop” is suppose to fire off whenever the application stops/shuts down. The anomaly here is that on a tomcat based red5 compilations (which is the default one) the “appStop” does not fire up. This is because the is no straight forward “hook” / “point of entry” to determine when the server core stops. Hence we need to create a “Shutdown Hook” to handle the server/application shutdown by ourself.
The best way to do this is to create a internal / private class in your Application class source. Sample:
/* ShutDown Hook for Red5 Application */
class ShutdownHook extends Thread
{
Application app;
public ShutdownHook(Application app)
{
this.app = app;
}
public void run()
{
// do something here
}
}
class ShutdownHook extends Thread
{
Application app;
public ShutdownHook(Application app)
{
this.app = app;
}
public void run()
{
// do something here
}
}
Next we relate it to our Application class by the “addShutdownHook” method. This method is not something for red5 only. Its the most common way to intercept and handle your java application shutdown. So in the Application class appStart() method we can add:
public boolean appStart(IScope app)
{
Runtime.getRuntime().addShutdownHook(new ShutdownHook(this));
return true;
}
{
Runtime.getRuntime().addShutdownHook(new ShutdownHook(this));
return true;
}
We add it to the appStart() method to make sure it is called only once.
Note how we pass the reference to the Application class itself to the constructor “ShutdownHook”. Now by defining the properties as “protected” or “public” you can access then when the application/server is shutting down and do any cleanup jobs that you may have.
