On Thu, 13 Sep 2007, Krzysztof Sobolewski wrote: > Lee Begg pisze: > > tpserver-cpp is currently single threaded, so this just comes naturally. > > In future, they might not always be in order. > > Then I'm glad that I accounted for that already ;) > > >> I designed PipelinedConnection to be able to > >> handle even intertwined and not-in-order responses) > > > > libtpproto-cpp's protocol layer also handles intertwined and out of order > > responses, mainly because when fetching orders from the server, it needed > > to request the order descriptions before it could finish decoding the > > order. > > I can now see how and why and I'm not really happy with that knowledge. > That's because it may be self-describing, but is not self-contained. To > properly decode Order frame I need info provided by the OrderDesc frame, > but this is very hard to get in my approach of autogenerated code. I have > an idea how to solve that, but it won't be pretty and will require some > user intervention :)
One thing that libtpclient-py does is to download all OrderDesc frames before getting the Order frame. libtpproto-cpp GameLayer (iirc) holds a cache of OrderDesc to avoid having to fetch them more than once. Eventually, the cache of OrderDesc frames would be filled before they are needed, like libtpclient-py does. > -KS Later Lee
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ tp-devel mailing list [email protected] http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel
