Tag Info

New answers tagged

0

If you want to start experimenting with client/server communication with Android and a web service you don't need to develop a fully blown RESTful API to do it (though there are very good reasons why you might want to use a RESTful API eventually when you've had enough experience to think about how to design it well). The first recommendation is to use ...


0

You don't mention how many users you think this thing is going to scale to, and if that number is unlimited or unknown (but growing) this isn't going to scale very well in the long run. One way to do this is that you keep a pool of authenticated user IDs with some sort of expiry value of 15 minutes or something. If a user makes a request, your logic should ...


3

Sit down and write the client/server properly yourself. If you are not willing to implement all of the protocol, just doing part of it can leave you with significant and strange breakages when some application tries to: prepare a statement iterate over a result set do a transaction (and a rollback!) do something 'at the same time' as another thing (can ...



Top 50 recent answers are included