Harvester Design

[conseo]

Hi M,

> Can we roughly summarize the design in ASCII?  We need an overview of
> how it works at the very top level, maybe something like this:
> 
> 
>                                    local UI      remote UI *
> 
>                                        | read        | read
> 
>                                        V             V
>            kick              store          read
>    Kicker ------> Harvester -------> Cache <----- CacheWAP
> 
> 
>    Component   Function
>    ---------   --------------------------------------
>    Kicker      Detect new post in remote archive
>    Harvester   Fetch post from remote archive
>    Cache       Store post locally
>    CacheWAP    Web API for remote reader of cache
>    UI          Show post to user, e.g. in TalkTrack *
> 
> 
> Is this correct?  If not, please make necessary changes.  Afterwards
> I'll ask questions about the details.
> 
> 
>   * The talk track (a remote UI) is labeled 2 in this mockup:
>     http://zelea.com/project/votorola/s/gwt/stage/_/mock/home-1.xht

I don't understand what "local UI" is supposed to mean. I see "Cache" as 
storage and (web) API for information retrieval. The "Cache" will only hold 
DiffMessages, not the complete communications stream. 

Besides that, the ASCII design matches my picture.

conseo