Below is the current product backlog for the Laharsub project, in priority order. Relative size estimate provided in brackets. Please share your opinion or share an idea by adding a comment below or starting a discussion.

  1. Notification streaming [5]. This is to enable a streaming mode where multiple notifications can be sent from the server to the client without buffering them in memory.
  2. Single message mode [2]. This is to add a mode where only the most recently published message is available to topic subscribers (useful in applications where only the most recent version of data is relevant).
  3. Security [8]. This is to enable HTTPS with server authentication, integrity and confidentiality, as well as client authentication and authorization.
  4. MSI installer [1]. This is to provide a better experience for installing binary releases.
  5. Windows Azure, single instance [3]. This is to enable deployment in Windows Azure using a single instance of a role (no scale-out).
  6. Self hosted scale-out extension [40]. This is to enable scale-out to several instances in a self-hosted environment (where any software can be installed).
  7. Windows Azure, scale-out to several instances [20]. This is to enable enable scale-out to several role instances in Windows Azure, possibly taking dependency on a technology only available in Windows Azure.
  8. Amazon EC2, single instance [5]. This is to create an image for Amazon EC2 to enable quick deployment of Laharsub backend in a single VM in EC2 (no scale-out).
  9. Amazon EC2, scale-out to several instances [20]. This is to enable enable scale-out to several VMs in Amazon EC2, possibly taking dependency on a technology only available in Amazon EC2.
  10. WebSockets [13]. This is to add support for the WebSockets protocol in addition to HTTP long polling.
  11. Short polling [2]. This is to add support for HTTP short polling in addition to HTTP long polling to address scenarios where the client is running in an older browser. 

Last edited Nov 1, 2010 at 12:58 AM by tjanczuk, version 3

Comments

clamont Apr 7, 2011 at 2:45 AM 
This may help in an Azure scale out deployment:
[Set up internal WCF communications between worker roles] http://msdn.microsoft.com/en-us/gg457887
[Azure Memcached implemented in AppFabric] http://blogs.msdn.com/b/windowsazureappfabric/archive/2011/04/05/windows-azure-appfabric-caching-article-in-msdn-magazine.aspx
[Silverlight scale out code] http://blogs.msdn.com/b/windowsazureappfabric/archive/2011/04/05/windows-azure-appfabric-caching-article-in-msdn-magazine.aspx
[More SL Scale out code] http://tomasz.janczuk.org/2009/09/scale-out-of-silverlight-http-polling.html

SilverlightStar Apr 1, 2011 at 11:42 PM 
I vote for Azure singe instance and scale out.

Antares19 Jan 7, 2011 at 1:05 AM 
My vote for "Security" and "host server in IIS" features.
ps: thanks for great application :)