What better server side technology to serve information to cross-platform software?

Asked

Viewed 176 times

-2

We know it’s possible to access the Facebook of various clients such as browsers, android, iOS etc. I know that via browser HTTP protocol is used (obviously) with technologies such as AJAX and Comet(chat, real time notifications).

Doubt:

What would be the best technology on the server side so that mobile platforms (android, iOS) and browsers can interact with each other?

TCP sockets? HTTP/Restful requests? SOAP?

I gave Facebook as an example, to understand what my need (cross-platform access).

Goal:

Develop cross-platform software with the same functionality independent of the platform.

android ios facebook http

  • Your doubt is unclear. Please edit and try to be a little clearer.

  • I edited. I had been confused because I do not know the keyword that defines my need, summarizing it would be a cross-platform software that needs to interact with each other independent of the platform.

  • @Gustavopiucco your question remains based on opinions and very broad. We deal better with questions that have well defined answers. This type of question fits better in some forum or discussion group.

  • "I know that via browser the HTTP protocol is used (obviously)" - And the Websockets being standardized by the W3C, are on the side? I think the trend is Realtime.

2 answers

1


As far as mobile customers are concerned, the only viable solution is the interfaces RESTFUL, that use HTTP and its different verbs: POST, GET, DELETE and PUT.

And having a robust and well structured restful inteface, you can serve any type of customer. I can’t say for sure how Facebook works, but I highly doubt it’s anything other than that.

1

Facebook uses various technologies to provide its various services. It is very difficult to stay here to mention here how each one works.

But for sure, the world is heading towards using Restful to integrate applications.

  • "the world is heading towards using Restful to integrate applications." - Why not Realtime? I think the trend is this, see the standardization of Websockets by W3C.

  • @Piovezan Also, this is an expensive complicated issue, which would render eternal discussions. But based on the great webservices today, I would say that the vast majority today is based on Restful.

  • 1

    The problem with Restful is the lack of scalability. Compare in this example 7.2 million Restful vs 50k Realtime requests.

Browser other questions tagged android ios facebook http

You are not signed in. Login or sign up in order to post.