What should happen when a client requests a POID?

客户机请求POID时会出现什么情况？

youdao

The factory requests a new account POID, and is assigned a range of 100 POIDs.

工厂请求一个新的帐户POID 时，服务会分配给它一组数目为 100 个的POID。

youdao

One approach to the problem uses a segmented POID address space (see References ).

解决该问题的一个办法是采用分段POID地址空间（请参阅 参考资料）。

youdao

That is to say, under no circumstances shall a non-unique POID be dispensed to a client.

也就是说，在任何情况下都不能给客户机分配不唯一的POID。

youdao

In particular, it would be unreasonable to assume that we could afford a database transaction per POID request.

特别是，想要为每个POID请求都提供一个数据库事务是不合理的。

youdao

The block maintains the value of the next valid identifier, and will provide the next PoId with the next method.

该块保留了下一个有效标识的值，并且会向下一个PoId提供next方法。

youdao

There is a POID class, a simple wrapper for the POID value, which insulates our APIs from the actual value type (primitive long in this case).

还有一个poid类，它是poid值的简单包装器，它使API与实际的值类型相分离(在这里是最初为long)。

youdao

We can provide clients an easy to use in-process component, which will be responsible for service location and communication, and POID block management.

我们可以为客户机提供一种易用的进程内(in - process)组件(负责服务定位和通信)以及POID块管理。

youdao

Now, add an attribute to the original purchaseOrderType, named purchaseOrderID, typed POID and stereotyped as «attribute», and finally, set the multiplicity to 0..

现在向原始的 apurchaseOrderType添加一个属性，名为purchaseOrderID、类型为 POID，原型为 «attribute»，最后将多重性设置为 0..

youdao

Now, add an attribute to the original purchaseOrderType, named purchaseOrderID, typed POID and stereotyped as «attribute», and finally, set the multiplicity to 0..

现在向原始的 apurchaseOrderType添加一个属性，名为purchaseOrderID、类型为 POID，原型为 «attribute»，最后将多重性设置为 0..

youdao