goat 0.3.12 → 0.3.13

data/bin/state-srv

@@ -26,7 +26,7 @@ module Goat
         @components_by_id = {}
         @components_by_page = {}
         @last_connected = {}
-        @first_connected = {}
+        @registration_times = {}
         @page_connections = {}
         @channelsrvs = {}
         @page_versions = {}
@@ -53,7 +53,7 @@ module Goat
 
       def initialize_page(pgid)
         @page_versions[pgid] = 0
-        @first_connected[pgid] = Time.now
+        @registration_times[pgid] = Time.now
       end
 
       def incr_page_version(pgid)
@@ -90,11 +90,11 @@ module Goat
         end
       end
 
-      def first_connected_delta(pgid)
-        if connected = @first_connected[pgid]
+      def registration_delta(pgid)
+        if connected = @registration_times[pgid]
           Time.now - connected
         else
-          $stderr.puts "ERROR: asked for first_connected_delta of #{pgid}, which I don't have"
+          $stderr.puts "ERROR: asked for registration_delta of #{pgid}, which I don't have"
           Time.now - Time.at(0)
         end
       end
@@ -213,8 +213,10 @@ module Goat
           # return newest components first
           @registry.components_by_class(msg['class']).\
             select{|c| c.spec == msg['spec']}.\
-            select{|c| @registry.connected?(c.pgid) || @registry.last_connected_delta(c.pgid) < 120}.\
-            sort_by{|c| @registry.first_connected_delta(c.pgid)}.\
+            select{|c| @registry.connected?(c.pgid) || \
+                          @registry.last_connected_delta(c.pgid) < 120 || \
+                          @registry.registration_delta(c.pgid) < 20}.\
+            sort_by{|c| @registry.registration_delta(c.pgid)}.\
             map(&:to_hash)
         end
 

data/goat.gemspec

@@ -1,6 +1,6 @@
 spec = Gem::Specification.new do |s|
   s.name = 'goat'
-  s.version = '0.3.12'
+  s.version = '0.3.13'
   s.summary = 'Pre-release beta version of Goat'
   s.author = 'Patrick Collison'
   s.email = 'patrick@collison.ie'
@@ -11,7 +11,6 @@ spec = Gem::Specification.new do |s|
   s.require_paths = %w{lib}
 
   s.files = %w{
-    README.md
     bin/channel-srv
     bin/press
     bin/state-srv

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification 
 name: goat
 version: !ruby/object:Gem::Version 
-  hash: 11
+  hash: 9
   prerelease: false
   segments: 
   - 0
   - 3
-  - 12
-  version: 0.3.12
+  - 13
+  version: 0.3.13
 platform: ruby
 authors: 
 - Patrick Collison
@@ -30,7 +30,6 @@ extensions: []
 extra_rdoc_files: []
 
 files: 
-- README.md
 - bin/channel-srv
 - bin/press
 - bin/state-srv

data/README.md

@@ -1,45 +0,0 @@
-Goat
-===
-
-<http://goatweb.org>
-
-Description
------------
-
-Goat makes it easier to build complex, data-heavy websites. It's written in Ruby, and aims to be a good tool for building applications in the class of, say, Facebook: data-heavy, interactive, and real-time.
-
-Web development presents a fairly subtle set of problems:
-
-- Distributing application logic between the client and the server. (You usually can't put it all on the client, but it's unpleasant to wait twenty seconds for a page to refresh before you find out the value of a form field is invalid.)
-- Figuring out how to make changes without interruption -- live data migrations, and code upgrades that (ideally) don't interrupt users.
-- Varying browsers.
-- Multiple programming languages (CSS, JavaScript, HTML, server-side languages).
-- Multiple input devices (touch, mouse, keyboard).
-- May have to scale massively at short notice
-
-Goat
-----
-
-Goat is page-oriented. Pages are the fundamental building block of the web. Complex data often naturally breaks down into discrete pages. In the URL, pages come with one of the most universally used and understood collaboration tools.
-
-Figuring out how to combine presenting a significant amount of data presentation with complex user interaction is tough. It's not easy to imagine what Facebook, Wikipedia, Twitter, Gmail or Quora would look like as desktop applications -- and it's unlikely that they'd be better.
-
-Some applications, such as spreadsheets, probably aren't a good fit for a page-based model, and these applications are not likely to be a good fit for Goat.
-
-Goat avoids HTML templates, and replaces them with programmatic HTML generation and components: a page is composed of one or more components. Components may persist on the server, if you'd like to be able to update the client-side state of a component in real time. Components also group together the code that may be required for a single UI element: client-side JavaScript, server-side Ruby, and CSS.
-
-Goat tries to:
-
-- Make it easy to build pages that don't require refreshing (i.e., live updating of data).
-- Optimize for the development cycle (all things being equal, the application that's easier to change will end up better).
-- Make writing client-side JavaScript easier. (Intelligent scoping, easy RPC.)
-- Make programmatic HTML generation easy.
-- Not be all-encompassing, but to make sensible assumptions about most parts of the web application stack.
-
-Design decisions
-----------------
-
-- Goat should store JS for some set of components in an external file so that JS can be cached across pages.
-- You can't have to load 2mb of JS and have a loading bar when a user visits the site for the first time. URLs should look decent.
-- Make site work well for search engines.
-- Goat doesn't try to abstract away the fact that the web is built with CSS/HTML/JavaScript.