- Boost - lists.preview.boost.org

[GSoC 2014] Http Server Proposal
by Vinícius dos Santos Oliveira 17 Mar '14

17 Mar '14

Hi guys, I'm interested in develop an asynchronous HTTP server for Boost as part of GSoC. The design would be inspired from Node.js without the facilities or inspirations that were created to overcome JavaScript quirks and limitations. The library would be modular to the point where you can use only small parts of it and you could also replace components that you don't like. The library should have a small overhead to be used on embedded projects, but the modular design will allow you to use higher abstractions when such concerns don't exist. Of course it's difficult to find the "right" answer to the problem, then I'll limit the higher-abstractions to "proven" techniques and avoid controversial features. I hope to give more details in the middle of the next week. The library will not be about writing template-driven web pages, but it will be about HTTP and you will be able to do things like video live stream via HTTP (try to do that with Django or PHP). I also intend to allow a efficient use in multithreaded environment with high-load of data (although network applications are usually I/O bound and not CPU bound). Of course it'll be possible to use WebSocket with this library too. Another thing I want to allow is to mock HTTP requests and transparently replace parts of the stack without affecting already written code. The purpose of this feature is to allow other transport mechanism such as FastCGI and also provide a future-proof approach by better allowing HTTP/2.0 when released. I would implement such library on top of Boost ASIO and I'd include facilities that I'm sure would work on long-term. Because the success of such project is very sensible to the chosen design, I'd limit its scope to things that I know it will work long-term. If the implementation project end up being too small, I can also implement WebSocket support (I had implemented it before and it wouldn't be such challenge for me), where the implementation effort is higher than the interface effort. I'm not sure about the deliverables (yet!), but I hope to give more details soon, once I have written nice texts. I'm particularly interested in an elegant way to represent some data structures, but I'll detail the plans soon (lots of text to write, ideas to explain and references to convince, among other). The text was a bit long, but it's because I already have something in mind. I hope to deliver a proposal explaining all the design, why I think it would work and other matters in the middle of the next week. I'm also open to suggestions and modifications in the not-yet-presented-proposal. I can provide background about my experiences later, but for now I want to know what do you guys think about the idea. TL;DR: For now I want to know what do you guys think about having a core HTTP server library in Boost. -- Vinícius dos Santos Oliveira https://about.me/vinipsmaker

7 23

Library metadata
by Daniel James 17 Mar '14

17 Mar '14

Hi, I'm starting to add metadata to modules for updating the website, and hopefully other uses in the future. I added the metadata to Boost.Unordered and Boost.Functional to give you an idea of what this will look like: https://github.com/boostorg/functional/tree/develop/meta https://github.com/boostorg/unordered/tree/develop/meta You can see several libraries listed in the Boost.Functional file. I'll write some documentation soon, but it should be fairly easy to understand. I basically took what was in the website library list and split it up into modules. Quick summary of the fields: key - Used to be the website to identify each library. Don't change it, or the website will think it's a new library. boost-version - The version in which the library was released. name - The name of the library. authors - The authors of the library - will probably add a 'maintainers' field later. description - Library description - this is used in the library list, so keep it short. std-proposal - Is the library proposed for the standard. std-tr1 - Is the library part of TR1. category - The categories the library belongs to. one element for each category. The documentation will include a list of available categories. documentation - Path to the documentation. The documentation field is optional. If it isn't included, it'll use the default path: /libs/module-name/. If it is included, relative paths are resolved relative to the module directory, absolute paths from boost root - although I'd suggest you always use a path within the module, and if there's only a single library in a module, use the default path. This isn't the final format - I think the standards status fields could do with an overhaul to support C++11 etc. You also don't need to write the initial files yourself, I'll generate them and create pull requests once this is settled. Let me know what you think. thanks, Daniel

8 15

Submitting Proposal
by Pulkit Mendiratta 17 Mar '14

17 Mar '14

Hello! I am not able to find a link to submit my proposal. After logging in to google-melange, and requesting a role from boost community, i am not able to find a link to submit it. -- Cheers, Pulkit Mendiratta

2 2

Possible problem in boost::enable_if_c or MSVC 11
by Emil Dotchevski 17 Mar '14

17 Mar '14

I've noticed that for some reason some of the tests of the QVM library (which is in the queue for Boost review) are failing on MSVC 11. The tests that fail use boost::enable_if_c. Before I investigate further, I'm wondering if anyone else has had problems with enable_if_c and MSVC 11 (this code works with earlier versions of MSVC and with GCC.) Thanks, Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode

1 0

Boost.odeint Applicant Test
by Zeshawn Shaheen 16 Mar '14

16 Mar '14

Hi, I am Zeshawn Shaheen, a junior at the University of the Pacific in Stockton, CA, US. I am a double major in computer science and mathematics and was interested in partaking in developing implicit routines for Boost.odeint. I've read in the Boost Developers Archive that a small test is given regarding the applicant's coding skills and the odeint library. I would appreciate it if I could be given the test. Thank you. Sincerely, Zeshawn Shaheen

1 0

[GSoC 2014] [Computation of generalized hypergeometric functions]
by Cosmin Boaca 16 Mar '14

16 Mar '14

Hello, I am Cosmin Boaca, and I want to contribute to boost during GSoC 2014. Here is my proposal [0] . Please give me some feedback about it. [0] https://www.google-melange.com/gsoc/proposal/review/student/google/gsoc2014… Thank you, Cosmin Boaca

4 6

Re: [boost] [GSoC] Boost.Thread executors proposal
by Ian Forbes 15 Mar '14

15 Mar '14

>First provide in addition a static polymorphic interface. The template >functions submit_at and submit_after would accept any chrono >`time_point` and `duration`. Is this with respect to the granularity of the time point? e.g. nano/micro/mille etc? If it is I'm assuming this would take an executor and then convert the time point to the desired granularity (nanoseconds by default) then add it to the executor. >Second, provide an adaptor that wraps an scheduled executor and makes it >a polymorphic one. Polymorphic with respect to what? >Third, provide an adaptor that wraps an executor, manage the time based >operations using a specific thread and forward all the operations to the >wrapped executor. So this would take a reference to an executor or a shared_ptr then spawn a single thread that would loop and add the submitted closures at the desired time to the given executor? Ian, ________________________________________ From: Boost [boost-bounces(a)lists.boost.org] on behalf of Vicente J. Botet Escriba [vicente.botet(a)wanadoo.fr] Sent: Friday, March 14, 2014 3:34 AM To: boost(a)lists.boost.org Subject: Re: [boost] [Boost.Thread][GSoC] Boost.Thread executors proposal Le 13/03/14 04:59, Ian Forbes a écrit : > Hi, > > Here is my GSoC proposal for working on the scheduled executors classes. It can be found here: www.cs.mcgill.ca/~iforbe/ > > This proposal mainly deals with the implementation of classes extending the `scheduled_executor` interface. I have already written thread pool implementations with very similar functionality to the ones proposed. > > I feel that the current proposal could use a little bit of touching up so please feel free to leave comments/criticisms. > > I would also be willing to take on any other work related to executors such the the dynamic/work-stealing thread pool implementation or the parallel algorithms library and add it into my proposal. > > Hi, I like your proposal on scheduled_executor and possibly extend it to a priority thread pool. I would let the work-stealing outside the proposal. Just to note that the closure would not be a std::function<void()> as this class doesn't accept a movable only function. Boost.Thread would include (version 1.56) a boost::executors::work as a type-erased class for closures. I'm looking for a different approach respect to scheduled work of the N3785 proposal. First provide in addition a static polymorphic interface. The template functions submit_at and submit_after would accept any chrono `time_point` and `duration`. Second, provide an adaptor that wraps an scheduled executor and makes it a polymorphic one. Third, provide an adaptor that wraps an executor, manage the time based operations using a specific thread and forward all the operations to the wrapped executor. What do you think of this approach? Best, Vicente _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

2 1

Re: [boost] [GSoC] pipelines questions
by Thaler Benedek 14 Mar '14

14 Mar '14

> I'm interested in the Boost.Pipelines proposal of GSoC 2014. [snip] Hi, I created a preview [0] with a working example. Please see the readme file and example/hello.cpp. This demo does not have parallel abilities and supports only 1-to-1 transformations in the pipeline. The purpose of this is to showcase my programming abilities and ask your opinions regarding the design and implementation. I intend to have this repository as a supplement of my proposal. Thanks, Benedek [0]: https://github.com/erenon/pipeline

3 7

Permissions in boost::iostreams::mapped_file output
by Patrick Reynolds 14 Mar '14

14 Mar '14

Boost folks, Working with mapped_files in a project, I recently discovered that the files were being written to disk with unexpected permissions on the linux systems. I discussed this further in a pull request here: https://github.com/boostorg/iostreams/pull/2 Is this the proper avenue for making such a contribution? If not, where can I go to get started. Thanks, Patrick

1 1

[modular-boost] Errors on submodule update
by Marcel Raad 14 Mar '14

14 Mar '14

Hi, I'm using TortoiseGit 1.8.7 with msysgit 1.8.5.2 on Windows and have checked out the develop branch of the boost repository. On every submodule update, I get the following errors. Is the submodule configuration corrupt? Git seems to believe that there are msm and polygon submodules which are not in the libs directory: ... git.exe submodule update -- "libs/msm" ... git.exe submodule update -- "libs/polygon" ... git.exe submodule update -- "msm" error: pathspec 'msm' did not match any file(s) known to git. Did you forget to 'git add'? git.exe submodule update -- "polygon" error: pathspec 'polygon' did not match any file(s) known to git. Did you forget to 'git add'? ...

1 0