﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Ayende Rahien commented on RavenDB Changes API on the wire</title><description>Beyers,
The custom config is done in code, and requires no config changes on IIS. 
You can run this on shared hosting</description><link>http://ayende.com/157281/ravendb-changes-api-on-the-wire#comment15</link><guid>http://ayende.com/157281/ravendb-changes-api-on-the-wire#comment15</guid><pubDate>Mon, 30 Jul 2012 17:03:09 GMT</pubDate></item><item><title>Beyers commented on RavenDB Changes API on the wire</title><description>Seeing that you have to configure special settings for IIS "turn off bufferring", does this mean anyone using shared hosting where you do not have administrative privileges on IIS will not be able to use this feature? </description><link>http://ayende.com/157281/ravendb-changes-api-on-the-wire#comment14</link><guid>http://ayende.com/157281/ravendb-changes-api-on-the-wire#comment14</guid><pubDate>Mon, 30 Jul 2012 11:10:53 GMT</pubDate></item><item><title>Bill commented on RavenDB Changes API on the wire</title><description>Seems silly.. Why not just use WebSync from Frozen Mountain?  Way more developed than what you're talking about.</description><link>http://ayende.com/157281/ravendb-changes-api-on-the-wire#comment13</link><guid>http://ayende.com/157281/ravendb-changes-api-on-the-wire#comment13</guid><pubDate>Sun, 29 Jul 2012 06:44:04 GMT</pubDate></item><item><title>Ayende Rahien commented on RavenDB Changes API on the wire</title><description>John,
See my post about SignalR.
I didn't feel like spending more time learning, testing and integrating another library (with the potential of discarding it in the end), where as I could spend a lot less time just building it myself.</description><link>http://ayende.com/157281/ravendb-changes-api-on-the-wire#comment12</link><guid>http://ayende.com/157281/ravendb-changes-api-on-the-wire#comment12</guid><pubDate>Fri, 27 Jul 2012 16:17:31 GMT</pubDate></item><item><title>john commented on RavenDB Changes API on the wire</title><description>Ayende,
Its interesting that you decided to roll your own solution. Usually its happening at the moment developer gets fed up with something and say - that's it I write my own!

As for everyone streaming data/notifications though HTTP you do face exactly the same challenges, nothing unique.

Question would be then, why not just use bosh with ejabberd, already proven/stable/scalable OS solution with multitude of extensions?  
Is it the same reason which brought you into writing your own solution?
</description><link>http://ayende.com/157281/ravendb-changes-api-on-the-wire#comment11</link><guid>http://ayende.com/157281/ravendb-changes-api-on-the-wire#comment11</guid><pubDate>Fri, 27 Jul 2012 16:10:39 GMT</pubDate></item><item><title>Ayende Rahien commented on RavenDB Changes API on the wire</title><description>Shane,
Oh, that shouldn't be an issue.
It is really cheap to do this sort of things. You might need special config to handle this (remove default concurrent connection limits), but that would be about it.
See how SingalR handles this</description><link>http://ayende.com/157281/ravendb-changes-api-on-the-wire#comment10</link><guid>http://ayende.com/157281/ravendb-changes-api-on-the-wire#comment10</guid><pubDate>Fri, 27 Jul 2012 15:31:48 GMT</pubDate></item><item><title>Shane commented on RavenDB Changes API on the wire</title><description>How many concurrent connections do you expect to handle or be able to handle.  I'm sure server hardware has a large impact, but on an average webserver is this just background noise or will the perf be noticeable.  I'm speaking more in general terms for this approach and not specifically how it works with RavenDB.  I'm looking at 5k concurrent connections likely to a single server in my scenario and am wondering if this approach would be feasible.</description><link>http://ayende.com/157281/ravendb-changes-api-on-the-wire#comment9</link><guid>http://ayende.com/157281/ravendb-changes-api-on-the-wire#comment9</guid><pubDate>Fri, 27 Jul 2012 15:28:47 GMT</pubDate></item><item><title>Ayende Rahien commented on RavenDB Changes API on the wire</title><description>Jonnii,
That is the idea, and it will be compatible with that when we release.</description><link>http://ayende.com/157281/ravendb-changes-api-on-the-wire#comment8</link><guid>http://ayende.com/157281/ravendb-changes-api-on-the-wire#comment8</guid><pubDate>Fri, 27 Jul 2012 14:23:16 GMT</pubDate></item><item><title>jonnii commented on RavenDB Changes API on the wire</title><description>this looks very similar to server side events in html5:

http://dsheiko.com/weblog/html5-and-server-sent-events/</description><link>http://ayende.com/157281/ravendb-changes-api-on-the-wire#comment7</link><guid>http://ayende.com/157281/ravendb-changes-api-on-the-wire#comment7</guid><pubDate>Fri, 27 Jul 2012 12:26:35 GMT</pubDate></item><item><title>Ayende Rahien commented on RavenDB Changes API on the wire</title><description>Olav,
We have heartbeat going on in there.</description><link>http://ayende.com/157281/ravendb-changes-api-on-the-wire#comment6</link><guid>http://ayende.com/157281/ravendb-changes-api-on-the-wire#comment6</guid><pubDate>Fri, 27 Jul 2012 12:12:45 GMT</pubDate></item><item><title>Olav commented on RavenDB Changes API on the wire</title><description>Interesting stuff. How do you detect dropped connections if nothing is going across? I mean how will the client know if the server has just disappeared?</description><link>http://ayende.com/157281/ravendb-changes-api-on-the-wire#comment5</link><guid>http://ayende.com/157281/ravendb-changes-api-on-the-wire#comment5</guid><pubDate>Fri, 27 Jul 2012 12:08:13 GMT</pubDate></item><item><title>Ayende Rahien commented on RavenDB Changes API on the wire</title><description>Tobi,
What mispelling?

Oh, I see this now.</description><link>http://ayende.com/157281/ravendb-changes-api-on-the-wire#comment4</link><guid>http://ayende.com/157281/ravendb-changes-api-on-the-wire#comment4</guid><pubDate>Fri, 27 Jul 2012 11:23:04 GMT</pubDate></item><item><title>tobi commented on RavenDB Changes API on the wire</title><description>I hope the misspelling in "InitializeConnetion" doesn't go into production as you will be stuck with it like with "Referer" ;-)</description><link>http://ayende.com/157281/ravendb-changes-api-on-the-wire#comment3</link><guid>http://ayende.com/157281/ravendb-changes-api-on-the-wire#comment3</guid><pubDate>Fri, 27 Jul 2012 11:13:36 GMT</pubDate></item><item><title>Ayende Rahien commented on RavenDB Changes API on the wire</title><description>Satish,
Typically, you have one request per client, and it isn't hold a great deal of resources, so I am not worried about it at all.</description><link>http://ayende.com/157281/ravendb-changes-api-on-the-wire#comment2</link><guid>http://ayende.com/157281/ravendb-changes-api-on-the-wire#comment2</guid><pubDate>Fri, 27 Jul 2012 10:20:35 GMT</pubDate></item><item><title>satish commented on RavenDB Changes API on the wire</title><description>HttpStreaming may need more resource incase if the server is holding the Request . So its better RavenDB should release a best practice document. it may be evil . Is it possible to switch to Web sockets if the implementation is available.  
           </description><link>http://ayende.com/157281/ravendb-changes-api-on-the-wire#comment1</link><guid>http://ayende.com/157281/ravendb-changes-api-on-the-wire#comment1</guid><pubDate>Fri, 27 Jul 2012 10:18:33 GMT</pubDate></item></channel></rss>