The other day we release Styx to the public. It has served us well over the years as the main protocol generator for Firebase, so we thought we should be a bit more transparent with it. Speaking of "it", here's what "it" is:
- A protocol format specified in an XML file.
- Binary and JSON packaging for the above.
- Automatic API generation in Java, C++, Flash, HTML5, etc...
So, the other day we released an RNG service to the wild. It is a Marsenne Twister implementation with background cycling and discarded draws. It's fast, secure and possible to drop right into you existing Firebase projects. Here's how: First, you
Background One of the great benefits with Firebase is the support for transparent failover. All you as a game developer have to do is to make sure that your game state is serializable. The Problem One common pattern that follows from this approach
Everyone agrees that good debugging is critical. But it is not entirely trivial when it comes to multi-threaded applications. Here's the story how I tracked down a nasty bug in the Java5 ReentrantReadWriteLock. Update 15/4: To be a bit clearer, the