2 more features off the top of my head:
* Google app engine compatibility
I looked at google app engine but it has a couple of gotcha's.
- Time per request: max 30 sec
Which effectively rules out longpolling.
- Memory cap 128MB.
Depends on how hard you are running it but if you run a large pool you may find this restrictive. A smallish pool will comfortably run in about 50mb but once you start scaling you are consuming memory two ways, first is caching work. Second is mapping work delivered to workers for current block and last block. I can't actually remember why I did this, it was partly to ensure no duplicate work but there was one other reason.
would you consider implementing poolserverj for appengine backends? requests can run indefinitely and they have 1GB ram. here is the spec:
https://developers.google.com/appengine/docs/java/backends/overviewi'd like to add a bitcoin pool to my web app's community, but everything is already on appengine and i don't want to have to glue it together with
ec2 AWS. if you could get it to run on appengine backends, i would be eternally grateful!
Show Posts
