Clever Geek Handbook

J2me Httpconnection which is better to get or post?

In J2ME, which connection type is better? Receive or publish. Which one is faster, which one uses less bandwidth and which one is supported by most phones? What are the advantages and disadvantages of both?

+2


source to share


3 answers


Also see Is there a limit on the length of a GET request? which can make a difference if you plan to abuse GET.



Remember that network operators (in the UK of course) have caching schemes that can affect your traffic.

+2


source


If you look at what Opera Mini does, they only use HTTP POST in their HTTP mode. I think this is a great idea due to the following reasons:

  • POSTs are never cached (at least according to the HTTP spec) - this saves you the trouble of caching statements, etc.
  • Some operators seem to do better with POST than GET - this is the feeling I get from what some Nigerian users are talking about.
  • Opera has the most installations of any J2ME application in the world, most likely, and if they do, it is probably safer.
  • No problem with HTTP GET request length limits.
  • You can use a more flexible data format if you like it uses less data (no data needed for data like with GET)


I think it is much cleaner but requires some additional work, for example. if you are using your HTTP web logs to parse the number of requests for "? type = blah", for example, you will have to move that into your site logic.

+2


source


If you follow standards get

, you should only use it to retrieve data and post

to add new items. It depends on the server handler implementation which is faster / slower.

+1


source






More articles:


All Articles