On Thu, 17 Jan 2008, nash wrote: > > So the only case that typeframe is option is in the TP03 objects? As > > TP03 is going away "real soon(tm)" why not just ignore this case? > > > > As there are no servers which are in "production use", there seems > > little reason to support TP03 and TP04 in a client library. > > So the current plan is to totally drop TP03 soon?
In tpserver-cpp, I generally only support two versions, the cutting edge latest version, and the one before it. So TP03 will not disappear, but if you see a spec for TP05 being developed, you shouldn't expect it to last much longer. We have only started on a further protocol version once the clients and servers have caught up. Last night I came to within 5 minutes of removing TP03 support from tpserver-cpp. Sometimes it's hard to support both.... > /me has been trying to make things in galaxie do both TP03 and TP04. > > Q: Is it worth taking the time to generate a list of TP04 features and > getting the appropriate people filling in the appropriate boxes for the > appropriate applications appropriately? In the feature matrices? Not a bad idea. > That way we can all see which parts of TP03 can be dropped for instance, > since we currently need hybrid clients and servers? TP04 is, for the most part, a superset of TP03 (with the exception of objects and some semantics around orders). Other than the exceptions, there isn't too much difference between the versions. > The client/server feature matrix on the webpage is pretty good (although > I think the server one could be expanded a lot)... Both are rather old now. It may be helpful to split the libraries out of the client matrix. Also, it is reasonably hard to update them in their current format. Maybe some PHP code could be written to produce them from an easier representation to edit. > Regards, > nash At some point, I intend to do some work on the website. We have also pondered changing to a wiki-style site. We should do some work on this. 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
