Java^™ Standard Fork-Join

Read a recent article on Fork-Join Processing by one of our developers about the issues with multi-core development and why you need this product.

You call the Tymeac Server (embedded or RMI) as you would for any simple client/server application
     passing a request for the server to work on and
     waiting for a reply with the results of the processing.

return_data = Tymeac.doWork(request);

Tymeac places your simple request

into a High Performance Priority Queue or uses fork-join logic to

fork (separate) your multi-part request

into its components and places each part into its respective High Performance Priority Queue.

A thread, in the thread pool of each Queue:

• fetches the request,
• executes the request by using reflection to call your logic module (user-written class),
• and returns any return data from your logic module to Tymeac.

For the simple request, Tymeac passes back the return data to the caller.

For the multi-part request, Tymeac concatenates the return data from all the parts into an Object array (joins) and returns that array to the caller.

  And there's more.  Lots, lots more, so keep reading.

• Are you aware of The Shadow of multi-threaded applications and how to Tame the Beast?

• Would you just like to place a request in a background queue and not have to bother writing all the code to control it? [example]

• Would you like to segregate processing into separate Java^™ Virtual Machines without the gargantuan overhead of commercial application servers?

• Do you need many flavors of RMI Servers from the simple to the complex?

• Would you like to run a backend queuing and threading server embedded within any application (including a Java ME (CDC) application?)

• Do you need a backend object for your Web Service (Jini^™ and eventually UDDI)?

• Is it too time-consuming to develop a custom container with prioritized queues and multi-threading capabilities that can handle
  Timed, Autonomous, Urgent and Multi-Component requests?

If you need a secure, reliable, manageable and fault tolerant backend process manager
        for any purpose and do not wish to start at the beginning designing and testing one yourself,
        then you need Tymeac^™

Tymeac™ provides a   prioritized queuing facility and   high-quality thread management in a   [separate virtual machine] with a   minimal footprint that is   easy to use.

---

		Tymeac™ is a backend-process container that manages persistence, messaging, queues, threads, stall detection and recovery, recursion, logging, statistics, the user interface and much more. Tymeac™ is a vendor-neutral, multi-platform, high performance, highly scalable software tool. Tymeac™ lets you focus on implementing software solutions to your problems instead of being in the software tool business.

Read articles on High Performance Queues and Managing Threads by one of our developers about the issues with Queues and Threads and why you need this product.

 

Download the latest Standard Edition (Java SE) at SourceForge.net Project=TymeacSE

Download the latest Micro Edition (Java ME) at SourceForge.net Project=TymeacME

 

Do you need a scaled down version?  Read a developerWorks article by one of our developers on how to build your own custom framework, complete with source code.

 

---

Segregation means placing the processing in an RMI Server. Clients may be EJBs, Servlets, Applets or other applications. Now -- why segregate an application? A portion of your application: has outgrown a single system's processing capability. has special processor requirements or needs to be readily portable. needs isolating because of security or data access reasons. needs a background function. An application needs concurrent access by a multitude of clients with load balancing. A large and/or complex application needs to implement a structure of independent agents. [ Details ]