List view

• v0.7

  Overdue by 10 year(s)

  •

  Due by December 31, 2015

  •0/3 issues closed
  0% complete3 open0 closed

• v0.6

  Issues I want solved for a v0.6 release.

  Overdue by 10 year(s)

  •

  Due by September 30, 2015

  •1/6 issues closed
  16% complete5 open1 closed

• Create basic Mesh formats for Serialization.

  We need to extend the base types of data that Remus understands to include a general mesh format, that is suitable for serialization.

  No due date

  •0/3 issues closed
  0% complete3 open0 closed

• Efficent Transmission of Large Data

  Currently the serialization code inside of Remus creates numerous temporary strings, and does more copies than required. Combine this with no support of transmitting existing data files, without requiring the user to read the files, and we don't have support for really large data. The goal is to be able to easily transmit large chunks of data, be it from already existing memory, or from a given file. If possible Remus will compress the data for wire transmission, decompressing on the worker without the user ever knowing. In the case of transmitting files, we will only read and send the data of files when the worker / server are on a remote machine.

  Overdue by 11 year(s)

  •

  Due by March 1, 2015

  •0/3 issues closed
  0% complete3 open0 closed

• Support for Custom Worker Factories.

  Currently custom worker factories are all saddled with file searching behavior, since we don't have a proper concept of a general worker factory. The goal for this milestone is to get multiple types of worker factories support in Remus. Easy goal would be to have a QtThreadPoolWorkerFactory, and the current ExecuteProcessWorkerFactory. A stretch goal would be to add a EC2WorkerFactory that was able to spawn and manage remote instances.

  No due date

  •1/2 issues closed
  50% complete1 open1 closed