You know, I've written network engines for games and stuff, but I've not yet looked into web sockets.  I'll have to look into that tomorrow.  I know there are some browsers that don't support it, so I should still have a fallback, even if I go that route.  Unless...  well, why don't you tell me how you would/do use it, and maybe I can get a glimpse of how I should be doing things. 

You're right!  Thank you for bringing that to my attention.  The functions for creating addresses or checking status requires a main password, but not a secondary.  (All transactions require both.)  That certainly helps make me feel better about using the Wallet API. 

Much obliged, friend!

I've not seen anything like this in the documentation, which asks specifically for the "main My Wallet password."  The "Passwords" section in Blockchain doesn't seem to indicate having multiple passwords to access the API, either.

If you happen to find what you recall, please let me know!  That would make me much more secure in putting those passwords on a server.

The two things I want to do seem very easy.

1) Create an address on-demand.

2) Monitoring the transactions on this address (amount + confirmations, specifically).

---

This can be done with the Receive Payments API by creating a forwarding address and listening to callbacks.  

Pros: Anonymous, doesn't require a My Wallet account, and no credentials are stored on the server (potential security risk).  

Cons: Callbacks happen only once every ten minutes, and there's no way to actively check the status of transactions.

---

This can also be done with the My Wallets API using the Create Address and Get Address Balance functions.  

Pros: Active polling means I can check whenever I want and don't have to rely on callbacks (sometimes a security concern).

Cons: I would need to include my Wallet Main Password (but not the Secondary Password) on the server so it can make the function calls.  Get Address Balance doesn't tell me how many confirmations it has, only whether or not it has the required number of confirmations (a function parameter).  (It's nice to show customers: "You have 3 of 6 required confirmations.")

---

So, help me talk it through and figure out which of these two implementations is better?  Thanks.