PHP creating a multidimensional array of message threads from a multidimensional array (IMAP)
My question is the following:
If you look below you\'ll see there is a datastructure with message ids and then the final datastructure containing the message detail
-
An implementation with branches (more complex then a single thread
array('5' => array(5,7,8)), but unless I was only talking to 1 person, threads always tend to branch for me personally, so I'll have to cope with the added complexity).num =* .next = >, 0 = no replies * .branch = >, 0 = no more branches * Keep in mind: _every_ message 'starts' a branch, but that may be empty. */ $nodes = array( 0 => array( 'children' => array())); $ids = array(); foreach ($threads as $key => $val) { list($treeid,$type) = explode('.',$key); switch($type){ case 'num': //the actual message number of this tree node //store id for retrieval later: $ids[$val] = null; if($val==0){ //return to root $nodes[$treeid] = &$nodes[0]; } else { if(!isset($nodes[$treeid])) $nodes[$treeid] = array(); $nodes[$treeid] = array_merge($nodes[$treeid],array( 'id' => $val, 'message' => &$ids[$val], 'treeid' => $treeid)); } break; case 'next': // 0 means no next message, anything else is a reply if (0!=$val) { if(!isset($nodes[$val])) $nodes[$val] = array('parent' => $treeid); $nodes[$treeid][] = &$nodes[$val]; } break; case 'branch': //0 means end of branch, a number means continue as sibling \ //so we need to know the parent if (0!=$val) { if(!isset($nodes[$val])) $nodes[$val] = array('parent' => $nodes[$treeid]['parent']?:0); $nodes[$nodes[$val]['parent']][] = &$nodes[$val]; } break; default: trigger_error("Unknown tree traverse-type: $type", E_USER_WARNING); } } //the great thing is we can get all our ID's at once: $keystofetch = implode(',',array_filter(array_keys($nodes))); $messages = imap_fetch_overview($imap,$keystofetch, FT_UID); foreach($messages as $message){ // you can of course store the _whole_ message in this thread like: // $nodes[$message->uid]['message'] = get_object_vars($message); // and do what you like with $tree[0]['children'] (be it a resursive array iterator, // or a resursive function, your pick. // However, for this example we are going to only set message to a string of p.o.c // (which is also nicer for our treeiterator) $ids[$message->uid] = $message->from.':'.$message->subject; } //let's show the result: $it = new RecursiveTreeIterator(new RecursiveArrayIterator($nodes[0]), RecursiveTreeIterator::BYPASS_CURRENT, CachingIterator::TOSTRING_USE_KEY); foreach($it as $key => $item){ echo "$key".(is_scalar($item)?': '.$item:'').PHP_EOL; } Which give us:
|-children |-0 | |-parent: 0 | |-id: 35 | |-message: Friend Purple Acc2A few things of note:
- The first incarnation of this script incorrectly added branches to the first child of a node instead of the actual node itself, which is fixed now by also storing its parent.
imap_threadisn't perfect: we seeid=9as an orphan, although it seems it should be in the first thread somewhere. However, due to the headers not mentioning this, Google Apps here decided to make it it's own node.- The 3rd (key=2) entry is a method to 'return to root', as the
N.num.N.branch,N.nextmethod has apparently no other way to return to root. This is the/return to root $nodes[$treeid] = &$nodes[0];bit. You can/should filter this out after determining all other nodes, but you need it to build the array at first.
To get only the nodes starting new threads (Nth reply on message, N>1):
$threads = imap_thread($imap, SE_UID); $branchestarts = array(); foreach($threads as $key => $value){ list($num,$type) = explode('.',$key); if ( $type=='num' // an id && $value == 0 // which is actually root && isset($threads[$num.'.next']) // then check for next && isset($threads[$threads[$num.'.next'].'.num']) ){ $branchestarts[] = $threads[$threads[$num.'.next'].'.num']; } else if( $type=='branch' // branch movement && $value != 0 // not back && isset($threads[$value.'.num']) // sanity: target exists && $threads[$value.'.num'] != 0 // and is not a return to root ){ $branchestarts[] = $threads[$value.'.num']; } } echo json_encode($branchestarts);Which gives us:
[35,15,46,33,48,47,9,49,50,32]And indeed, 35,49,50 & 32 are starts of threads, 9 is recognized as such by the imap server too, and the rest are 2nd or more replies starting their own branches.
Now, you could indeed split out branches as seperate conversation, but as you can see, these are often only 1 or 2 replies more, longer threads tend to develop a bit more rarely. To see how these 'branches' go:
$branches = array(); $currenttree = null; foreach($threads as $key => $value){ list($num,$type) = explode('.',$key); switch($type){ case 'num': //nothing break; case 'next': if(is_null($currenttree)) $currenttree = &$branches[$threads[$value.'.num']]; if($value && isset($threads[$value.'.num'])) $currenttree[] = $threads[$value.'.num']; break; case 'branch': unset($currenttree); if($value && $threads[$value.'.num']){ $branches[$threads[$value.'.num']] = array($threads[$value.'.num']); $currenttree =& $branches[$threads[$value.'.num']]; } } } echo json_encode($branches, JSON_PRETTY_PRINT);Which gives you roots & branches & their replies:
{ "35": [ 35, 7, 11, 39, 40, 38, 12, 25, 19, 23, 30, 2, 20, 1, 41, 27, 17, 31, 4, 37, 24, 13 ], "15": [ 15, 18, 45 ], "46": [ 46, 29, 26, 34 ], "33": [ 33, 36, 10 ], "48": [ 48 ], "47": [ 47, 5, 3, 21, 8, 43, 28, 42, 22 ], "9": [ 9 ], "49": [ 49 ], "50": [ 50 ], "32": [ 32, 16, 14, 6, 44 ] }With some slight alterations we can get the messages in there:
$branches = array(); $currenttree = null; $messages = array(); foreach($threads as $key => $value){ list($num,$type) = explode('.',$key); switch($type){ case 'num': //nothing break; case 'next': if(is_null($currenttree)) $currenttree = &$branches[$threads[$value.'.num']]; if($value && isset($threads[$value.'.num'])) $currenttree[] = &$messages[$threads[$value.'.num']]; break; case 'branch': unset($currenttree); if($value && $threads[$value.'.num']){ $branches[$threads[$value.'.num']] = array(&$messages[$threads[$value.'.num']]); $currenttree =& $branches[$threads[$value.'.num']]; } else { $currenttree = null; } } } $keystofetch = implode(',',array_filter(array_keys($messages))); foreach(imap_fetch_overview($imap,$keystofetch,FT_UID) as $message){ $messages[$message->uid] = $message; } echo json_encode($branches);//won't show it's output, this answer is to large as it is ;)Another option is to just sort them by datetime value, which would be alright for conversations with little/negligible branching, probably making most of the code you are planning just work.
A combination of the two would be 'moving branches', follow threads in series, so this:
1 2013-06-01 2 2013-06-02 3 2013-06-03 4 2013-06-03 5 2013-06-04Becomes a sequence of
1,2,3,4,5but a reply on3would resort it:1 2013-06-01 4 2013-06-03 5 2013-06-04 2 2013-06-02 3 2013-06-03 6 2013-06-05Making it a sequence of
1,4,5,2,3,6, which would keep it a logically flowing conversation, with always the thread/branch with the last reply as last.
加载中...
- 热议问题