移动设备之间通信位置

发布于 2024-09-25 09:06:58 字数 215 浏览 7 评论 0原文

我只是在这里集思广益。假设我有 2 个移动设备,iPhone、Android、WinPhone7、BlackBerry、Palm 等等。我想将我的位置(纬度/经度)从我的设备传送到另一台设备。这样做的最佳方法是什么?

假设每个设备都具有内置地图功能或定制的本机应用程序。

我提出了一些想法,例如短信/彩信或嵌入链接的电子邮件。然而,它们似乎都很笨拙。

还有其他想法吗?

I am just brainstorming here. Let's say I have 2 mobile devices, iPhone, Android, WinPhone7, BlackBerry, Palm, whatever. I'd like to communicate my location (latitude/longitude) from my device to another one. What is the best way of doing this?

The assumption that each device has either built-in mapping capabilities or a custom-built native app.

I've thrown around ideas like SMS/MMS or email with links embedded in them. However, they all seem to be cludgy.

Any other ideas?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

水溶 2024-10-02 09:06:58

每部手机都可以轮询位置变化的网络服务(或者,如果您必须且不关心安全性,则可以使用 Twitter)可能会奏效。显然,网络服务必须接受坐标,并且能够轮询每个设备的更新。安全性显然是一个问题,但这可能是另一种方法,前提是每个设备都有一个自定义应用程序来完成此任务,并且可以通过网络访问来轮询更改。

A web service (or, if you must and don't care about security, Twitter) that each phone could poll for changes to location might work out. The web service would have to accept the coordinates, obviously, plus be able to be polled for updates by each device. Security is obviously a concern, but that might be another way to go provided that each device had a custom app to accomplish this task as well as web access to poll for changes.

注定孤独终老 2024-10-02 09:06:58

我会选择短信。它保证私密、可靠、低成本且易于使用电池。

Web 服务也是一种选择,但是:

  • 隐私是一个问题,因为数据将离开移动运营商内部网络
  • 可靠性 - 那么,您必须构建自己的消息传递系统这总是会导致
  • 最终用户成本失败 - 为了访问 Web 服务,最终用户必须激活数据会话,而持续的轮询可能会成为大量流量的来源。
  • 开发成本 - 您需要开发该网络服务
  • 电池寿命 - 对数据连接的持续轮询会对电池产生影响。

与短信相比:

  • 隐私 - 短信永远不会离开运营商网络,因此保证它与您的电话一样私密。
  • 可靠性 - 您的移动运营商保证短信中心始终在那里接受您的消息
  • 最终用户成本 - 在大多数网络中,短信成本可以忽略不计
  • 开发成本 - 嗯,由于短信中心已经存在,您无需任何额外的努力即可使用它(不包括需要发送和接收这些短信的软件)
  • 电池寿命 - 没有不利对电池的影响

无论如何,这两种设备仍然必须有一个“地图应用程序”,您可以对其进行编程以与 SMS/网络服务数据进行交互。

I would go for SMS. It is guaranteed to be private, reliable, low-cost and easy on battery.

Web service is also an option, however:

  • privacy is a concern, as the data will leave mobile operator internal network
  • reliability - well, you would have to build your own messaging system and that can always fail
  • end-user cost - in order to access web service, end-user would have to activate a data session and constant polling can be a source of significant traffic.
  • development cost - you would need to develop that web service
  • battery life - constant polling over the data connection will have an effect on the battery.

Compare that with SMS:

  • privacy - SMS never leaves operator network, so it is guaranteed to be as private as your phone calls are.
  • reliability - SMS center is guaranteed to always be there by your mobile operator to accept your messages
  • end-user cost - in most networks, SMS cost is negligible
  • development cost - well, as SMS center is already there, you can use it without any additional effort from your side (excluding your soft that needs to send and receive those SMSs)
  • battery life - no adverse effect on battery

In any case, both devices still have to have a "mapping app" that you can program to interface with the SMS/web-service data.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文