What kind of device are you using exactly, something like this or something more sophisticated / configurable? If we assume that the device sends its data over TCP, I would consider the following approach with separate input/output processes:
Input: a process listening specific TCP port and storing incoming coordinates to database with a device id. Preferably, your listening loop must be able to handle simultaneous connections without them blocking each other.
Output: web application reading coordinates from database for a given device id and displaying them through the Google Earth API.
Use whatever programming language(s) you are familiar with.
For me there is a technical limitation/risk here -> the mobile device, and its connectivity.
1) What are your requirements? Do you need to support various mobile devices or will you focus on only one platform ?
2) More importantly, you have to understand that GPRS data connections differ from a PC connected to the Internet. There are various connection restrictions imposed by different mobile operators.
If I was to design such a system in order to minimise those risks I would go with a web server running on port 80 which the mobile devices would upload their Long/Lat through POST (or even GET to simplify things).
EDIT: Regarding scalability, it would be very easy to scale things up in the future using tried&tested load-balancing techniques.
EDIT2: Whichever technology you decide to use, i would HIGHLY recommend that the first thing you do is to mock up a prototype. Those connection restrictions could be show-stoppers. Ideally you need to explore them before you have made any serious investment.
发布评论
评论（2）
您到底使用哪种设备，例如这个或更复杂的设备/ 可配置？如果我们假设设备通过 TCP 发送数据，我会考虑使用单独的输入/输出进程的以下方法：
输入：监听特定 TCP 端口并使用设备 ID 将传入坐标存储到数据库的进程。最好，您的监听循环必须能够处理同时连接，而不会相互阻塞。
输出：网络应用程序从数据库中读取给定设备 ID 的坐标，并通过 Google 地球显示它们API。
使用您熟悉的任何编程语言。
What kind of device are you using exactly, something like this or something more sophisticated / configurable? If we assume that the device sends its data over TCP, I would consider the following approach with separate input/output processes:
Input: a process listening specific TCP port and storing incoming coordinates to database with a device id. Preferably, your listening loop must be able to handle simultaneous connections without them blocking each other.
Output: web application reading coordinates from database for a given device id and displaying them through the Google Earth API.
Use whatever programming language(s) you are familiar with.
对我来说，这里存在技术限制/风险 ->移动设备及其连接。
1) 你的要求是什么？您是否需要支持各种移动设备，还是只专注于一种平台？
2) 更重要的是，您必须了解GPRS 数据连接与连接到互联网的PC 不同。不同的移动运营商施加了各种连接限制。
如果我要设计这样一个系统以尽量减少这些风险，我会使用在端口 80 上运行的 Web 服务器，移动设备将通过 POST（甚至是 GET 来简化事情）上传其经度/纬度。
编辑：关于可扩展性，将来使用经过尝试和测试的负载平衡技术来扩展规模将非常容易。
编辑2：无论您决定使用哪种技术，我强烈建议您做的第一件事就是模拟原型。这些连接限制可能会成为阻碍。理想情况下，您需要在进行任何认真的投资之前探索它们。
For me there is a technical limitation/risk here -> the mobile device, and its connectivity.
1) What are your requirements? Do you need to support various mobile devices or will you focus on only one platform ?
2) More importantly, you have to understand that GPRS data connections differ from a PC connected to the Internet. There are various connection restrictions imposed by different mobile operators.
If I was to design such a system in order to minimise those risks I would go with a web server running on port 80 which the mobile devices would upload their Long/Lat through POST (or even GET to simplify things).
EDIT: Regarding scalability, it would be very easy to scale things up in the future using tried&tested load-balancing techniques.
EDIT2: Whichever technology you decide to use, i would HIGHLY recommend that the first thing you do is to mock up a prototype. Those connection restrictions could be show-stoppers. Ideally you need to explore them before you have made any serious investment.