Made 1.5 pc-side web, recently switched to a mobile app project, responsible for interface development
The phone is different from the PC, to consider the traffic and power, and the interface of a small amount of data, the number of requests and concurrency is relatively higher
So what are the features of the app interface?
Is it necessary to do various object-oriented complex encapsulation?
Is there a need to use frames? Which is the right one?
Reply to discussion (solution)
interface and the PC is no different, write the object JSON output data can be, as for the flow and power problems of the mobile phone to select the data problem
interface and the PC is no different, write the object JSON output data can be, as for the flow and power problems of the mobile phone to select the data problem
In fact, the flow and power, I do not understand the Android, do not know how to optimize, nothing but the return of the JSON, as far as possible to extract the same string out
The main question is still on the frame
As long as there is data transfer, traffic must exist. Reduce the flow of data on the compression of redundancy
More power when sending data than when receiving data, since the less you send the better
It's better to use frames than not to use frames, because at least now you don't know much about mobile communications.
To be familiar with later, then decide the frame of choice
As long as there is data transfer, traffic must exist. Reduce the flow of data on the compression of redundancy
More power when sending data than when receiving data, since the less you send the better
It's better to use frames than not to use frames, because at least now you don't know much about mobile communications.
To be familiar with later, then decide the frame of choice
To compress redundant data, we should look at the design of the data structure.
Now very confused about the framework of the problem, I just took over the code, the PC-side management background is thinkphp, mobile API is native, only include a dbconnect, each database operation is mysql_query, but looked at the former author's code, The level in my mind does have a big big question mark
The framework may be too redundant on the phone interface, but I also want to encapsulate some data filtering, communication authentication encryption, caching, data model for the object of the Operation interface and so on, at present, I can not write the level of the complete thing, just the product on the line without considering the load concurrency, perhaps the first to use the framework for more appropriate
At present the most familiar is TP, heard that CI is very lightweight also turned over some documents, Xu big or passers-by can recommend a suitable framework for the app interface?
Apart from the phone directly related to the service side is no different, is not to provide data
As long as there is data transfer, traffic must exist. Reduce the flow of data on the compression of redundancy
More power when sending data than when receiving data, since the less you send the better
It's better to use frames than not to use frames, because at least now you don't know much about mobile communications.
To be familiar with later, then decide the frame of choice
To compress redundant data, we should look at the design of the data structure.
Now very confused about the framework of the problem, I just took over the code, the PC-side management background is thinkphp, mobile API is native, only include a dbconnect, each database operation is mysql_query, but looked at the former author's code, The level in my mind does have a big big question mark
The framework may be too redundant on the phone interface, but I also want to encapsulate some data filtering, communication authentication encryption, caching, data model for the object of the Operation interface and so on, at present, I can not write the level of the complete thing, just the product on the line without considering the load concurrency, perhaps the first to use the framework for more appropriate
At present the most familiar is TP, heard that CI is very lightweight also turned over some documents, Xu big or passers-by can recommend a suitable framework for the app interface?
What's so tangled about this? Output phone want to get the JSON data, and then after the mobile phone to accept the processing, the use of caching mechanism of what is the problem of mobile phone, as for the optimization of the interface is data query optimization and reasonable allocation of data, the left should not have some of the removal, JSON data is generally small the largest number of K just. In short, the interface is to do the JSON output is good
If the interface is written on the server side, do not need to consider the problem of power, the same as the Web API to do.
Just return using JSON format.
The service side is no need to consider the phone charge, you just pay attention to the traffic, and now basically return the JSON format of the data, it is in the return of data considerations, only provide the necessary fields, to avoid unnecessary field redundancy, as for the framework, see their own trade-offs, as well as the framework of understanding, suggest the initial frame bar
Thank you for starting with the PC-side web-based approach to develop a trial version of thinkphp
