Created
April 26, 2012 19:39
-
-
Save nlacasse/2502438 to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Hi Kai, | |
We pushed the ETag fixes this morning. You should now see the requests to '/' come back with 304s, which your browser will handle correctly. Hopefully this will speed things up for you. | |
Also, I recommend that you try the newest version of spire.io.js javascript library. There were a few poorly optimized requests in there. | |
Here are answers to your other questions: | |
> 1. As far as I understand the plans, I don't pay for open connections, but | |
> only for messages I publish? Or does a "connection" requires bandwidth? | |
An open connection does not count as bandwidth. When the connection is closed, some data may be sent, and that data will count towards the bandwidth. So there is no difference in cost between a request that returns instantly, and one that stays open for a minute. | |
> 2. What browsers do spire.io.js support, is IE7 included? | |
It works for sure on FF >= 4.0, Chrome and IE9. | |
I only have IE9, but it has "IE8 Mode" and "IE7 Mode", and the library works in those, so I'm confident that it will work in a "real" IE7 or IE8 browser. Although I'm not sure | |
> 3. Publishing a message with the ruby client takes about 1,5s | |
> : https://gist.github.com/f2fffee06e8701de7d27 . Is there anything I can do | |
> for speeding this up? | |
These delays seem to be caused by network latency. We are investigating latency issues now. | |
Getting a bogus resource (like with "time curl https://api.spire.io/blahblah") should tell you what the latency between you and the server is, because those 404s are sent very fast (<10ms). | |
> 4. As I said before I want to share subscriptions between page loads. Does | |
> it make sense to create the subscription on the server and associate it with | |
> the user's session? So if a user have opened several tabs with my | |
> application, all Spire connections would "use" the same subscription? Or do | |
> I have to create seperate subscriptions? | |
You can certainly re-use subscriptions. Subscriptions can have names, and one use case is to have one subscription per user. There are methods to getSubscriptionByName which help with this. | |
Of course, you could create seperate subscriptions for each tab if you want to. | |
Thank you very much for this feedback. It is very helpful to have get such great feedback from across the globe! | |
Please let me know how else we can help you, | |
-Nick |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment