• <div><p>how can I use ownership percentage to build my lineups</p><p>该提问来源于开源项目：DimaKudosh/pydfs-lineup-optimizer</p></div>
• <div><p>We might want to consider transfer of ownership from to . Currently Google searches point to . Another issue is that the code in forked repos cannot be searched within Github. <p>...
• <div><p>You mentioned in the README that you would be interested in transferring ownership to someone who is interested in maintaining the project. The company I work for ...
• <div><p>let's not pollute the other isssue. <p>I didn't see any ownership transfer request yet</p><p>该提问来源于开源项目：zimbatm/ffmpeg-static</p></div>
• <div><p>Given that there are several feature requests open in the issues and that this project lies at the heart of many Rust projects, would you be open to transferring ownership of the repository &...
• <p>As you were maintaining everything in this project I think is fair I transfer the repository ownership to you. The only thing I need you to do, if you want to, is to rename or delete your fork so I...
• re the most active here in replying to issues and pull requests, would you be interested in us transferring ownership to you?</p><p>该提问来源于开源项目：hraban/tomono</p></div>
• <p>This adds the concept of ownership to cookbooks and also allows addition and deletion of collaborators. Note that I had to enable Postgres' trigram extension for full text search because the ...
• d rather find someone else to take ownership. Takers? I know you've been pretty active on issues/PR's, would you be interested? Still happy to chime in on design or code reviews, just don'...
• <div><p>Starting to implement ownership cleanliness based on https://docs.google.com/a/dimagi.com/document/d/12WfZLerFL832LZbMwqRAvXt82scdjDL51WZVNa31f28/edit#. </p> <p>This currently <em>only</em> ...
• <p>Is it ok if you keep ownership and I continue with write access? <p>OTOH, if you don't want to continue owning this repo, I could take care of it. <p>Regards,</p><p>该提问来源于开源项目：...
• <p>Is available and willing to transfer ownership of this repository and the associated project on <a href="https://crates.io/crates/libusb">crates.io</a>? <p>Ditto for ...
• takeownership of any file you want and make owner
• <div><p>So due to overwhelming feedback, it looks like the ownership urls will look like this: <pre><code> http://jsbin.com/remy/canvas/12/edit </code></pre> <p>The aim is to have a login-less system...
• <div><p>A significant portion of my ownership plot is taken from contributors whose files I deleted. <p>To reproduce: <pre><code> hercules --burndown --burndown-people --pb ...
• 9.OWNERSHIP OpenDDS: The OWNERSHIP policy controls whether more than one Data Writer is able to write samples for the same data-object instance. Ownership can be EXCLUSIVE or SHARED. Below is the
https://download.csdn.net/download/eidolon_foot/12568768

9.OWNERSHIP

OpenDDS:

The OWNERSHIP policy controls whether more than one Data Writer is able to write samples for the same data-object instance. Ownership can be EXCLUSIVE or SHARED. Below is the IDL related to the Ownership QoS policy:

OWNERSHIP策略控制着一个以上的Data Writer是否能够为同一数据对象实例编写样本。 所有权可以是独占或共享。 以下是与所有权QoS策略相关的IDL：

enum OwnershipQosPolicyKind {

SHARED_OWNERSHIP_QOS,

EXCLUSIVE_OWNERSHIP_QOS

};

struct OwnershipQosPolicy {

OwnershipQosPolicyKind kind;

};

If the kind member is set to SHARED_OWNERSHIP_QOS, more than one Data Writer is allowed to update the same data-object instance. If the kind member is set to EXCLUSIVE_OWNERSHIP_QOS, only one Data Writer is allowed to update a given data-object instance (i.e., the Data Writer is considered to be the owner of the instance) and associated Data Readers will only see samples written by that Data Writer. The owner of the instance is determined by value of the OWNERSHIP_STRENGTH policy; the data writer with the highest value of strength is considered the owner of the data-object instance. Other factors may also influence ownership, such as whether the data writer with the highest strength is “alive” (as defined by the LIVELINESS policy) and has not violated its offered publication deadline constraints (as defined by the DEADLINE policy).

formal/2015-04-10:

This policy controls whether the Service allows multiple DataWriter objects to update the same instance (identified by Topic + key) of a data-object.

此策略控制服务是否允许多个DataWriter对象更新数据对象的同一实例（由Topic +键标识）。

There are two kinds of OWNERSHIP selected by the setting of the kind: SHARED and EXCLUSIVE.

通过该类型的设置可以选择两种所有权：共享和专有。

SHARED kind

共享种类

This setting indicates that the Service does not enforce unique ownership for each instance. In this case, multiple writers can update the same data-object instance. The subscriber to the Topic will be able to access modifications from all DataWriter objects, subject to the settings of other QoS that may filter particular samples (e.g., the TIME_BASED_FILTER or HISTORY QoS policy). In any case there is no “filtering” of modifications made based on the identity of the DataWriter that causes the modification.

此设置表明服务不会对每个实例强制执行唯一所有权。 在这种情况下，多个编写者可以更新同一数据对象实例。 主题的订阅者将能够访问所有DataWriter对象的修改，但要遵守可能过滤特定样本的其他QoS的设置（例如TIME_BASED_FILTER或HISTORY QoS策略）。 在任何情况下，都不会基于导致修改的DataWriter的身份对修改进行“过滤”。

EXCLUSIVE kind

专有种类

This setting indicates that each instance of a data-object can only be modified by one DataWriter. In other words, at any point in time a single DataWriter “owns” each instance and is the only one whose modifications will be visible to the DataReader objects. The owner is determined by selecting the DataWriter with the highest value of the strength26 that is both “alive” as defined by the LIVELINESS QoS policy and has not violated its DEADLINE contract with regards to the data-instance.

Ownership can therefore change as a result of (a) a DataWriter in the system with a higher value of the strength that modifies the instance, (b) a change in the strength value of the DataWriter that owns the instance, (c) a change in the liveliness of the DataWriter that owns the instance, and (d) a deadline with regards to the instance that is missed by the DataWriter that owns the instance.

因此，所有权可能会发生变化，因为（a）系统中的数据编写器具有更高的修改实例的强度值，（b）拥有该实例的数据编写器的强度值发生变化，（c）拥有该实例的数据编写器的活跃度发生变化，以及（d）关于实例的截止日期，该截止日期被拥有该实例的数据编写器错过。

The behavior of the system is as if the determination was made independently by each DataReader. Each DataReader may detect the change of ownership at a different time. It is not a requirement that at a particular point in time all the DataReader objects for that Topic have a consistent picture of who owns each instance.

It is also not a requirement that the DataWriter objects are aware of whether they own a particular instance. There is no error or notification given to a DataWriter that modifies an instance it does not currently own.

也不要求DataWriter对象知道它们是否拥有特定实例。 没有错误或通知给DataWriter，它修改了它当前不拥有的实例。

The requirements are chosen to (a) preserve the decoupling of publishers and subscriber, and (b) allow the policy to be implemented efficiently.

选择这些要求是为了（a）保持发布者和订阅者的分离，以及（b）允许有效地实施该策略。

It is possible that multiple DataWriter objects with the same strength modify the same instance. If this occurs the Service will pick one of the DataWriter objects as the “owner.” It is not specified how the owner is selected. However, it is required that the policy used to select the owner is such that all DataReader objects will make the same choice of the particular DataWriter that is the owner. It is also required that the owner remains the same until there is a change in strength, liveliness, the owner isses

a deadline on the instance, a new DataWriter with higher strength modifies the instance, or another DataWriter with the same strength that is deemed by the Service to be the new owner modifies the instance.

Exclusive ownership is on an instance-by-instance basis. That is, a subscriber can receive values written by a lower strength DataWriter as long as they affect instances whose values have not been set by the higher-strength DataWriter.

专有所有权是基于实例的。 即，订户可以接收由强度较低的DataWriter写入的值，只要它们影响其值尚未由强度较高的DataWriter设置的实例即可。

The value of the OWNERSHIP kind offered must exactly match the one requested or else they are considered incompatible.

提供的OWNERSHIP类型的值必须与请求的值完全匹配，否则将被视为不兼容。

10.OWNERSHIP_STRENGTH

OpenDDS:

The OWNERSHIP_STRENGTH policy is used in conjunction with the OWNERSHIP policy, when the OWNERSHIP kind is set to EXCLUSIVE. Below is the IDL related to the Ownership Strength QoS policy:

当OWNERSHIP类型设置为EXCLUSIVE时，OWNERSHIP_STRENGTH策略与OWNERSHIP策略结合使用。 以下是与所有权强度QoS策略相关的IDL：

struct OwnershipStrengthQosPolicy {

long value;

};

The value member is used to determine which Data Writer is the owner of the data-object instance. The default value is zero.

值成员用于确定哪个Data Writer是数据对象实例的所有者。 默认值为零。

formal/2015-04-10:

This QoS policy should be used in combination with the OWNERSHIP policy. It only applies to the situation case where OWNERSHIP kind is set to EXCLUSIVE.

此QoS策略应与OWNERSHIP策略一起使用。 它仅适用于将OWNERSHIP种类设置为EXCLUSIVE的情况。

The value of the OWNERSHIP_STRENGTH is used to determine the ownership of a data-instance (identified by the key). The arbitration is performed by the DataReader. The rules used to perform the arbitration are described in 2.2.3.9.2, EXCLUSIVE kind.


展开全文
• The ownership lifecycle seems to have a gap in it. We have an object whose ownership we would like to pass from player to player. The ownership transfer is initiated by each individual player when ...
• <div><p>I am still using alfresco-repository as repo and main-dev-coupling-data.json remains empty although code-ownership-report.json has 4000+ entries for the range 2017-06-01 to 2017-11-01. ...

...