On Wed, 2008-01-16 at 23:16 +1100, 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?
As in sometime before the end of this year (depending on the amount of development time I have). > /me has been trying to make things in galaxie do both TP03 and TP04. I don't see a good point of trying to support TP04 unless you need features which are not yet implemented by the servers. > 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? I agree that this would be a good idea. As Lee said, change the current stuff to this isn't all that easy at the moment (tables in HTML suck). Maybe something with Google Docs could be a good interim measure? > That way we can all see which parts of TP03 can be dropped for instance, > since we currently need hybrid clients and servers? Yes, I agree. This should be less of a hassle from TP04->TP05 as we can support "mix frames" in one connection. TP05 should be much more incremental (new frames and backwards compatible frames) then TP04 is. I will also do up a "summary" of all of TP04 document just before LCA. > The client/server feature matrix on the webpage is pretty good (although > I think the server one could be expanded a lot)... > > Regards, > nash Tim 'Mithro' Ansell _______________________________________________ tp-devel mailing list [email protected] http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel
