关于Windows 8近场接近实现规范的问题

本文介绍了关于Windows 8近场接近实现规范的问题的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

我应该在哪里询问有关

Windows 8近场接近实施规范的问题？

Where should I ask the question for clarification regarding

Windows 8 Near Field Proximity Implementation Specification?

如果它在这里，这里有一个问题：

If it is here, here is a question:

规范定义了一个用例场景：

The specification define a usecase scenario:

点按并启动是推出应用的体验。 使用此体验，运行已编程为API的应用的用户可以通过将其PC轻触其他设备来邀请其他用户运行相同的应用。 将邀请第二位用户启动相同的应用。

Tap and Launch is an experience for launching apps. Using this experience, a user running an app that has programmed to the API can invite another user to run the same app by tapping his PC to another device. The second user will be invited to launch the same app.

这可以是个人用例或人际用例。

This can be either a personal or interpersonal use case.

用户想和他的朋友一起玩游戏。 他启动了应用。该应用程序可能会提示他将他的PC用于另一台PC。

第二个用户没有运行应用程序，但安装了它。 邀请她启动该应用。 如果她拒绝邀请，则没有任何反应。

如果她接受邀请，则应用程序启动。用户现在可以一起玩游戏。

A user wants to play a game with his friend. He starts the app. The app may prompt him to tap his PC to another PC.

The second user is not running the app but has it installed. She is invited to launch the app. If she declines the invitation, nothing happens.

If she accepts the invitation, the app starts. The users are now able to play the game together.

另一方面，应用程序启动的唯一地方被描述，位于：

On the other hand, the only place where application launch is decribed, is in:

"AppLaunch：WriteTag"发布是一种应用程序只需将"Windows.windows/AppLaunch"消息写入标记的方法。

An "AppLaunch:WriteTag" publication is a means for an app to simply write a "Windows.windows/AppLaunch" message to a tag.

这两个定义相互矛盾，因为第一个定义了绑定2个设备并在其中一个设备上启动应用程序。

These 2 definitions contradict, since first one defines taping 2 devices with launching the application on one of them.

第二个定义简单的"WriteTag"。可以执行的操作以及某些其他设备可以读取标签，例如一周后。

The second one defines simple "WriteTag" operation that can be performed and some othere device can read the tag, for example a week later.

如果我理解正确，"AppLaunch"应该在没有"WriteTag"的情况下定义发布，因此当收到这个paublication时 - 它不会被写入标签，而是（可能通过SNEP）传递给任何可用的设备以立即启动应用程序。

If I understand correctly, "AppLaunch" publication should be defined without "WriteTag", so when this paublication is received - it will be not written to tag, but passed (via SNEP probably) to any available device for immediate application launch.

有人可以帮助我解决我的困惑。

Can someone please help me with my confusion.

Evgeny

推荐答案

虽然我也读过这个技术，但是基于 doc文件和MSDN文档 PublishBinaryMessage 功能，"LaunchApp：WriteTag""是一种协议，它是在您从设备发布消息时使用的，当使用此协议时，消息字符串将包含 launchArgs和 appName，以便终点设备将根据协议进行分析和读取消息并执行操作。 Though I am also just read this tech, but base on the doc file and the MSDN document forPublishBinaryMessage function, the "LaunchApp:WriteTag" is a protocol, it is used when you publish a message form the device, when use this protocol the message string will contain thelaunchArgs andappName so that the end point device will according to the protocol to analysis and read the message and do the action.