 |
| Asynchronous Middleware for Parallel Systems |
|
|
|
 Problems |
|
Problems with Race Conditions |
Race conditions occur when a process started ‘after’ another process actually finishes ‘before’ the other one. This is an unexpected happening and can always occur in parallel running concurrent systems when because of a traffic jam the process that started earlier, in fact reaches later than the other one.
Race conditions can be non critical in nature but at times they are ‘critical’. A critical race condition is defined as one that can either result in a wrong output or can push the system to an unstable state.
The race conditions are solved by purposefully introducing synchronization primitives like Mutexes. Here one process waits on the Mutex until the other process is done.
AMPS never has any race conditions introduced because of its very design. There may be race conditions in the network (which can be made part of FSM) but there are never any race conditions introduced by the parallel execution of code. |
|
|
| News & Events |
|
1st October 2009
A complete Service Delivery Platform for telecommunications applications is released all built on top of AMPS. SDP is showcased name Augur is available at http://Augur.biz
1st July 2009
AdvOSS launches a complete Diameter AAA server built on AMPS. The server is tested with very high load of millions of subscribers and worked well.
1st April 2009
AdvOSS launches full suite of Diameter applications built on top of AMPS. These include a HSS (Home Subscriber Server), Offline Charging and Online Charging. These complete a full suite of AAA applications for IMS (IP Multimedia Sub-System)
1st Jan 2009
Diameter Stack Launched. AdvOSS has launched a full Diameter protocol stack. This protocol is at the heart of next generation AAA and requires implementations that support higher processing and require scalability. This stack is now an integral part of AMPS.
|
|
|
|