How's about you go back 5 posts and read the authoritative answer on
the topic.
I see the post on the JSON-RPC interface, and apologize for not noticing it earlier. See below on how my point regarding a merchant-specific API still stands.
Perhaps I was not clear on this earlier.
Also: there's a whole host of features in Armory that would be essential
on a merchant site : offline txs and multi-wallets to name a few.
Offline wallets are useful to merchants, but would obviously never be connected to the website directly. I never said Armory wouldn't be useful to merchants, I said I believed it would never (never is a strong word, let's say "in the near future") have an API for
merchant-specific interaction.
So, next time, get brain in gear before dumbly applying pressure
to caps lock key.
Ad hominem attacks? Classy!
I feel we are digressing from the topic on hand, but I'd like to sum up by saying that, and this is with etotheipi's own words, that Armory is a "client". It is not a daemon. It is not a server.
It is a client. While it may be or become useful to merchants, it is, in its current incarnation, a client.
It will probably never be able to reach the speed of the compiled C++ daemon.
I'm also uncomfortable seeing Red Emerald compare Armory with bitcoind: "[...] Armory will be far better than bitcoind." That is like comparing apples to oranges.
It does not compute.If you would like to continue this discussion, please create a new topic, or send me a PM. I feel at least I've littered this thread enough. Sorry!