On Tuesday 30 April 2013 19:04:59 Jeff Garzik wrote: > The format currently used by bitcoind would be just fine -- > blocks/blkNNNN.dat for raw data, size-limited well below 1GB. Just > need to add a small metadata download, and serve the raw block files.
That doesn't seem very generic. It's tied far too much to the current storage format of bitcoind. Wouldn't it be better to add support for more bitcoin-protocol-oriented HTTP requests? Then any client can supply the same interface, rather than being forced to create blkNNNN.dat on the fly? http://bitcoind.example.com/block/BBBBBBBBBBBBBBBBBBBBBBB http://bitcoind.example.com/tx/TTTTTTTTTTTTTTTTTTTTTTTT http://bitcoind.example.com/block/oftx/TTTTTTTTTTTTTTTTTTT http://bitcoind.example.com/peers http://bitcoind.example.com/peer/nnn Essentially: block explorer's raw mode but in every bitcoind. The hardest operation for light clients is finding out the block that contains a particular transaction -- something that bitcoind already knows. I'd like to see support for HTTP POST/PUT of signed transactions and block announcements too. Andy -- Dr Andy Parkins andypark...@gmail.com ------------------------------------------------------------------------------ Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with <2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
