Projects

Terracotta

Terracotta provides clustering for Java applications. Features include: - High level replication - Cross JVM coordination - Large virtual heaps - Fine-grained changes - Runtime management and control - No serialization

MathBench

Mathbench is a Python IDE intended for the development of short scripts such as those daily used when doing research in applied mathematics and physics. Simple widgets and a strong plugin system make it useful and extensible.

evercookie-applet

Java Applet Persistence for Evercookie

la-school

A PHP based community system fo my personal community. Just playing around at the moment, but someday it will be finished and used for my community. Project will include things like role-based usermanagement, picture gallery, message board. Everything will be build on functions and classes so ... [More] it's easy to manage. This isn't really something you should use, because it's made to work for my needs =) [Less]

login3

this is a simple php login class i wrote for use with all of my sites for the past 4 years or so. you tell it what database to pull the username from, the columns for the user_name and password, whether or not you used crypt() on the password in the database, what you want the session name to be ... [More] , and it will go ahead, try to login, then spit back a nice session hash containing information from columns you chose for it. its nothing spectacular, but im putting it on google code for the sake of putting it on google code [Less]

authlib

Authlib is a powerful Object Oriented Cookie+MySQL driven user+session management system. It enables a secure environment using advanced encryption using MD5 (Message-Digest 5). Download Authlib @ SourceForge

phpsessionmanager

This project contains the code from this blog post on Carsonified. Updated 9/24/09 UsageStarting the session is a simple call to the "sessionStart" static function. // Creates a basic session. SessionManager::sessionStart('InstallationName'); // Creates a session thats ends ... [More] when the browser closes and is only accessible at www.site.com/myBlog/ SessionManager::sessionStart('Blog_myBlog', 0, '/myBlog/', 'www.site.com'); // Creates a session thats ends when the browser closes and is only accessible at https://accounts.bank.com/ SessionManager::sessionStart('Accounts_Bank', 0, '/', 'accounts.bank.com', true);You can manually set a session id to regenerate using the regenerateSession function. This is useful for when you change authentication states (the user logs in or out) as it also invalidates the old session. // Regenerate the session. SessionManager:: regenerateSession();FeaturesProtects against fixation attacks by regenerating the ID periodically. Prevents session run conditions caused by rapid concurrent connections (such as when Ajax is in use). Locks a session to a user agent and ip address to prevent theft. Supports users behind proxies by identifying proxy headers in requests. Handles edge cases such as AOL's proxy network and IE8's user-agent changes. [Less]

x3dcom

Experimenting with X3D, AJAX, and Servlets

memcache-cluster-failover-php

Memcache Persistent ClusterThis library includes PHP classes to define a memcached cluster, with a persistent storage. Imagine the next scenario: a) You have a cluster with several www servers, and you don't have a load balancer with sticky sessions, or maybe you have it, but you really want ... [More] to share the load between servers. So sticky sessions is not the best option. Or b) You have public servers and you want to do dns load balancing. But the thing is that you don't want to keep only some sessions, you want to save sessions for months, so this cache storage must be much bigger than a couple of GB. And of course, it must be fast! In these situations, you usually save the user sessions in a fast storage, and where all your servers can access, which is usually memcached. Sharedance would be an option, but: a) If you use 1 sharedance server, it's a single point of failure. If this server goes down, we loose all the cached data. b) If you use 2 sharedance servers, they should share a common filesystem. But if this filesystem is down ( any network problem, or the server with that filesystem crashes) you loose all the data, because it's saved in the filesystem. At this point, Memcached is the key. The first step is create a memcached cluster , saving the keys with fail tolerancy.This means that every key is saved in 2 nodes. With 2 memcached servers we have failover, but the total available space is the same as having only local memcached. Now we arrive at the case that a session is removed from memcached, because the available size is completely used, but you need it to keep in any persistent storage, like a database or shared filesystem, so when your customer comes back you remember him. Then, my friend, we arrive at this project. Our project is designed to provide you the right tools to solve this problem in your PHP application. In the first version, for persistent storage we only had filesystem based class. So it means that our servers must share any nfs directory. All the writes to persistent storage are executed in background, so you don't have to worry about performance. Filesystem consistancy is not a problem in this approach, because the same key will only be written from one instance at each time. For the next version, maybe we define a mutex for the writing process. The second version includes Data Base persistent storage. So we will have many tables where we storage the sessions, usually there is a database exclusively for this purpose. for Version 3, we are preparing a cluster client sql class, so access ( read and write ) will be done randomly to any of the mysql hosts in the database cluster. We have in mind another storage systems like mogilefs from danga , and hdfs ( hadoop ) , for future implementations. We are also looking at sphinx specification for this purposes. After some benchmarking maybe we will include it. [Less]

Zebra_Session

Zebra_Session is a PHP class that acts as a wrapper for PHP’s default session handling functions but instead of storing session data in flat files it stores them in a MySQL database, thus providing both better security and better performance. The Zebra_Session class is also a solution for ... [More] applications that are scaled across multiple web servers (using a load balancer or a round-robin DNS) and where the user’s session data needs to be available. Storing sessions in a database makes them available to all of the servers! Zebra_Session‘s code is heavily commented and generates no warnings/errors/notices when PHP’s error reporting level is set to E_ALL. [Less]