Hi Cassio,
Just got done listening to your CogCon presentation ... so .. chunks! I
think you hit the nail on the head with the concept of "chunks". It is
maybe the #1 most important (hardest) part of the design. Let me explain
why...
I (recently) took two extremely-naive attempts at implementing distributed
atomspace -- atomspace-ipfs and atomspace-dht (see the github repos) and
since I was naive, these efforts... well, they work, but they don't scale.
The core problem that wrecks both of those was the problem of "chunks" --
of knowing when two atoms are "near" each other. Of knowing when a glob of
atoms should travel together, should be lumped together. Without knowing
what belongs to a glob, a chunk, it was hard/impossible to have a good,
scalable backend.
... and if you do know how to identify the boundaries of a glob, then
almost all of the other aspects of building a distributed atomspace become
"easy".
Clarifying this makes all the other problems go away (or turn into problems
that any programmer can implement, without major stumbling blocks) .. so
any thoughts, work to clarify the idea of "chunks" would be ... well, for
me, it would be extremely important.
-- linas
--
Verbogeny is one of the pleasurettes of a creatific thinkerizer.
--Peter da Silva
--
You received this message because you are subscribed to the Google Groups
"opencog" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/opencog/CAHrUA37bz5CN%2BvDGXsy%3DFCcNjp_TY4ivNuDWN51LgdPCdawnSg%40mail.gmail.com.
