« Architecture » : différence entre les versions

De Assothink Wiki
Aller à la navigation Aller à la recherche
Contenu ajouté Contenu supprimé
(Page créée avec « The 3 possible architectures are: *Java emulation of assothink on 1 machine, 1 process, multiple threads. This is the first tested architecture of assothink. It ran from 20... »)
 
Aucun résumé des modifications
Ligne 1 : Ligne 1 :
The 3 possible architectures are:
The 3 possible architectures for Assothink (active jelly part) are:


*The basic architecture
*Java emulation of assothink on 1 machine, 1 process, multiple threads. This is the first tested architecture of assothink. It ran from 2010, on the Matscape machines.
*The intermediary architecture
*The dream: a dedicated set of millions of microchips, each working autonomously. This might be suggested to some company producing wide scale IC (integrated circuits) products. This would be the most achieved and performing version of Assothink.
*The target architecture
*Intermediary, DPDM. Many machines connected in a TCP-IP network, one or many small process per machine. Java emulation.


Its is important to note that the passive jelly construction has nothing to do with these 3 architecture. The construction of the passive jelly is a previous step.
It is important to note that the passive jelly construction has nothing to do with these 3 architecture. The construction of the passive jelly is a previous step.

== Basic architecture ==

Java emulation of assothink on 1 machine, 1 process, multiple threads.

Available as GWT application working within a browser. Check it at [[www.assothink.com|www.assothink.com]].

This is the first tested architecture of assothink. It ran from 2010, on the Matscape machines.

== Target architecture ==

The dream: a dedicated set of millions of microchips, each working autonomously, intensively computing and mainly exchanging signals.

This might be suggested to some company producing wide scale IC (integrated circuits) products. This would be the most achieved and performing version of Assothink.

== Intermediary architecture ==

This is a compromise.

The goal is to maximize computing speed at a reasonale price (this written in 2012).<br>

==== DPDM architecture ====

Many machines connected in a TCP-IP network, one or many small process per machine. Java emulation, thus java programming.

Version du 21 octobre 2012 à 11:56

The 3 possible architectures for Assothink (active jelly part) are:

  • The basic architecture
  • The intermediary architecture
  • The target architecture

It is important to note that the passive jelly construction has nothing to do with these 3 architecture. The construction of the passive jelly is a previous step.

Basic architecture

Java emulation of assothink on 1 machine, 1 process, multiple threads.

Available as GWT application working within a browser. Check it at www.assothink.com.

This is the first tested architecture of assothink. It ran from 2010, on the Matscape machines.

Target architecture

The dream: a dedicated set of millions of microchips, each working autonomously, intensively computing and mainly exchanging signals.

This might be suggested to some company producing wide scale IC (integrated circuits) products. This would be the most achieved and performing version of Assothink.

Intermediary architecture

This is a compromise.

The goal is to maximize computing speed at a reasonale price (this written in 2012).

DPDM architecture

Many machines connected in a TCP-IP network, one or many small process per machine. Java emulation, thus java programming.