Note that there are some explanatory texts on larger screens.

plurals
  1. POMost lightweight method of data for Android-consumed web service
    primarykey
    data
    text
    <p>I'm working on an Android app that consumes a web service that has the potential to return quite a lot of data. The web service is also goingto be built by my team, and we're looking into ways of transferring data to the client with the least amount of load. We've looked into REST and SOAP, and can't decide between the two. Would JSON be a good alternative? We might need to fetch quite a lot of data in some use cases.</p> <p>We'd really rather not use SOAP, if can avoid it. The emphasis is on reducing the work needed to be done on the Android system as much as possible.</p> <p>Could anybody please help us out? As far as technology scope is concerned, we have full freedom of choice as long as we stay within the JAVA umbrella.</p> <p>Thanks in advance.</p> <p>EDIT: Not sure how to add comments, so I'll do it here(I read the FAQs, but couldn't find the necessary section)</p> <p>Hi,</p> <p>Let me start by apologising for my vague problem statement, I was actually a bit rushed when I posted the query. Anyway, to answer your questions, by "a lot of data", I mean that there are going to be ba few large requests(2-3, depending on the use case) that MIGHT return a lot of data, e.g. if I search using the entity name(complete or partial), the result, which is going to be textual data only, would be considerably less than if the serach was made with country as a search parameter, in which case it might return several hundred separate results. One particular search parameter has the potential to return a few thousand rows of data. What we can control is the amount of data in each row(so to speak) returned. Currently, we're attempting to reduce the items to display per row(we're attempting to keep it below 5). It's a business decision, I'm afraid, so if we're stuck with the current scenario of 12 items per row, we need to be prepared for that as well, I'm afraid.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload