简体繁体 English

为什么Seam对话ID（CID）不按顺序排列

[英]Why Seam conversation id (cid) does not go sequencial order

原文 2011-06-15 10:24:11 2 1 seam-conversation

I have a problem at seam conversation. 我在接缝谈话时遇到问题。

I know that conversation id works in sequencial order when i see at url bar (http://myprojectname/login.xhtml?cid=1). 我知道当我在网址栏（http：//myprojectname/login.xhtml？cid = 1）看到会话ID时，它按顺序顺序工作。 But in my program , I first begin conversation and cid is 1 (http://myprojectname/login.xhtml?cid=1) and then i begin nest conversation and cid becomes 4 (http://myprojectname/register.xhtml?cid=4). 但是在我的程序中，我首先开始对话，并且cid为1（http：//myprojectname/login.xhtml？cid = 1），然后开始嵌套对话，并且cid变为4（http：//myprojectname/register.xhtml？cid = 4）。 Why does it happen? 为什么会发生？

In successful program, cid is 1 after that cid is 2 and then 3, 4 for new nested conversation. 在成功的程序中，cid为1，之后cid为2，然后3、4表示新的嵌套对话。 But we wonder why conversation id becomes 1 and then 4. 但是我们想知道为什么对话ID变成1然后是4。

Please explain me. 请给我解释一下。

1 个解决方案

There are different potential causes of your "problem". 您的“问题”有多种潜在原因。 In your case, I suppose, cid=1 and cid=2 were temporary conversations, used by login-redirection, cid=3 is long-running and cid=4 is nested one. 在您的情况下，我想cid=1和cid=2是临时对话，由登录重定向使用， cid=3是长时间运行的，而cid=4是嵌套的。

In general, urls are not the best place to track conversation usage/management. 通常，URL并不是跟踪对话使用/管理的最佳位置。 Seam doesn't economize on cid's, the only thing which is guaranteed is that cid's always grow. Seam不会节省cid的费用，唯一可以保证的是cid一直在增长。

So, I would not worry about that.. 所以，我不用担心。