lloydhilaiel

Ack! Acronym collision! EBS is Elastic Beanstalk, or Elastic Block Store?

If the former, it's in my opinion a question of what you're looking for. Here's my best response: https://hacks.mozilla.org/2013/05/introducing-awsbox-the-diy...

For what it's worth, there is a complementary (early stage) project a colleague of mine is working on where the idea is to let you leverage cloud formation from the command line and get closer to what you're talking about (deployment of a more complex infrastructure rather than just a single instance):

https://github.com/mozilla/awsboxen

That was specifically for the example server - if each request uses 5ms of processor time, (1000 ms / s) / (5 ms / req) == (200 req / s)

https://gist.github.com/4532177#file-application_server-js-L...

like, make you a smoothie? Or do this: https://github.com/lloyd/node-toobusy/blob/master/toobusy.cc...

I agree. /me fixes

Our problem is the the number of simultaneous connections we can support isn't static, it varies depending on the type of traffic bursts (i.e. New vs. Returning users).

But agree that a higher level proxy is useful - because this way your overloaded application doesn't even need to deal with traffic (we hope to use toobusy to have applications instruct the routing layer to temporarily block / reroute traffic in times of load).

"Two-character ASCII strings are not permitted, to avoid conflicting with current and future country codes based on the ISO 3166-1 standard."

See https://github.com/ozten/TLD.js/issues/8

the include file is about 4.7k minified and compressed. You don't need to include it in head, that's lame. we'll update the docs.

lloyd

Hi MatthewPhillips,

That's just the license header that's not stripped. I agree, that's a bit draconian. lemme see if I can fix that for you.

lloyd

As for streaming JSON parsers: https://github.com/lloyd/yajl

Around for four years. Stable. Language bindings for all major languages.

I hope to build jsonselect support on top of yajl and expose it as a native command line tool, so fast stream based filtering... but that's still ideaware at this moment :)

with the reference implementation:

JSONSelect.match(".nonexistantkey .somechild", obj) returns []

Alternately, if you use the JSONSelect.forEach() method your callback will just not be invoked.

So no existence testing before access for recursive values. A main benefit of this thing in javascript.

one way you can do native code integration with chromeless is using JSCtypes: https://wiki.mozilla.org/JSctypes

I hacked up a trivial proof of concept on this branch: https://github.com/mozilla/chromeless/tree/jsctypes_play

file system access, yeah! It should feel like node.js (on purpose): http://mozilla.github.com/chromeless/#guide/filesystem-acces...

databases, IndexedDB should "just work", and thinking exposing SQLlite is worthwhile.

only the most basic network libraries at the moment.

totally. check out webian: https://github.com/webianproject/shell

it's homegrown. I spun off the docstract project which pulls docs outta .js and outputs them in json. From their you can render the docs however you want. Docstract itself is permissive open source you can use, here:

https://github.com/lloyd/docstract