Hi, Again: If there would be a reimplemenation of tntnet there would be some functionality in there, which is generic enough to be put into a separate library. So there won't be ever never a tntnet without cxxtools or whatever you want to call the separate library.
And for http 2.0: I would rather implement http 2.0 in cxxtools and reuse it in tntnet. Http 2.0 can be used in xmlrpc or jsonrpc over http also. So it is the other way around: more cxxtools for less tntnet. More generic code and less specific. Tommi Am 15.08.2014 15:30, schrieb Ralf Schülke: > Hi Tommi, > sure cxxtools are good and we have cxxtools. Need we this for tntnet http 2.0 > ? > > We can go 2 way: > Impement http 2.0 in tntnet with cxxtools > or > Implement with less cxxtools, when we this way go then have we new > goals to make some nice thinks. > > The other way is we dont work on tntnet for http 2.0. > > Ralf > > 2014-08-15 15:17 GMT+02:00 Tommi Mäkitalo <[email protected]>: >> Hi, >> >> what is the problem with the dependency to cxxtools? >> >> If someone develops a concrete software product there are always some >> modules, which are not specific to that product and may be used in other >> products too. It makes sense to make them reusable. And it makes sense >> to move that generic code into a separate module, so that someone, who >> wants to reuse that code, get a chance to get it without taking the >> whole software product. >> >> And that is exactly, what tntnet and cxxtools is. When I developed >> tntnet, there were generic functionality, which I split into the generic >> reusable toolbox cxxtools. >> >> There are users out there, who for some reason do not need tntnet but >> like to use cxxtools, since it has so many useful things. I know that >> Andreas is one of them. >> >> So what is the advantage not to use cxxtools? The advantage of the >> separation is, that someone can use cxxtools without a web application >> framework. >> >> >> Tommi ... ------------------------------------------------------------------------------ _______________________________________________ Tntnet-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tntnet-general
