What should happen when a client requests a POID?

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

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

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

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

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

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

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

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

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

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

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

Listing 7 shows how to use a join with both relational and XML predicates and return, for each Purchase Order, the POID, and customer name.

清单7显示了如何使用关系和xml谓词合并J SONx，并为每个Purchase Order返回POID和客户名。

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)。

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块管理。

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..