From: Peter S. <si...@cr...> - 2007-05-21 04:22:34
|
Hi Dean, > A suggestion would be to have that class under the > boost/network/ directory. This would yield something like a > 'boost/network/uri.hpp' header which can be used on its own. Yes, for an Uri class that's perfectly reasonable, but for other classes things are not that obvious. The rfc2822 parsers, for example, are, well, parsers. They will typically be applied to data that comes from the network, but the need to parse an e-mail address can just as well arise in a spreadsheet program. Adding those parsers into a boost/network/rfc2822/ hierarchy does make sense to a degree, but it doesn't feel like the natural choice -- particularly considering the fact that those parsers will never depend on anything else in the network hierarchy. I still can't quite imagine what the scope of this whole endeavor is. Right now, I have a hard time seeing how my code fits in. >> What are the components we anticipate to have in cpp-netlib? > > Definitely a URI class would be a good idea. Right, an URI class would be great to have. Are there any other components we anticipate or would like to implement? What is the goal for cpp-netlib? When it's all done and accepted into boost, what does it contain? I'm sorry for bringing up those very general questions instead of committing code, but it feels important to develop some sort of shared vision. I have my code in a publicly available repository already; so it doesn't feel like I'm gaining a lot by checking it into this repository instead. I would do so because I'd hope that the code might become part of a team effort. At the moment, I can't quite say where exactly that team effort is headed. It would be nice to develop that notion. Best regards, Peter |