Yatao Li

@PhilPJL you should start a TrinityClient pointing at port 5304, not 80. Port 80 greets the client with a http message but it's really looking forward to a trinity handshake...

@PhilPJL I think the query example in the readme is compatible with the film dataset: ``` Freebase .StartFrom(530972568887245, select: new[]{"type_object_name"}) .FollowEdge("people_person_spouse_s") .VisitNode(Action.Continue) .FollowEdge("people_marriage_spouse") .VisitNode(Action.Return, select: new[]{"type_object_name"}); ```

@PhilPJL oops, looks like I broke the SQLite part.. I was working on cross-platform and wasn't sure about the dependencies... Will look into this today!

We're discussing about the UI part. I'll let you know when more information is available.

@ItFly thanks for the suggestion. Yes we do not intend to bind to a specific logger; I’m only hoping to keep the log hook really lean and mean, and all...

@jkliss could you attach the log for the two instances?

@eosfor if there's only OutEdge and a single node type Node, you'll have to do the check on the next hop, to examine the `Label` field, if I understand correctly....

Yes I fully agree with you about external mix and match -- not all filesystem X work well with notify tool Y. So this issue is about an extra/ folder...

In earlier versions of Trinity (back in 2011 or so) we've had auto-initialized fields. Unfortunately we observed a significant performance impact -- it would be much slower to allocate these...

Each local memory storage consists of 256 memory trunks, and each trunk is capped at 2GB so.. Looks like it's getting a little bit unbalanced. How are the IDs generated?...