Comments (7)
The problem here is that between boost 1.6 and 1.7 they seem to have changed completion_condition()
function.
We are developing and testing with boost 1.7, ipkn/crow uses boost 1.5
from crow.
Is this a problem to update to the newest boost @choice17 ? ;)
from crow.
Is this a problem to update to the newest boost @choice17 ? ;)
Not really, however, it would be nice to have it compatible to lower version.
from crow.
I'm not sure if that's a good idea. It requires additional work and it looks like a quirk in only one version of boost.
from crow.
we could potentially add a macro to check the boost version, and add a warning at the start of the application that "support for boost versions below 1.7 is deprecated and will be removed in a future release" just as a transition, this check would need to be added to the parts that @mrozigor changed while adding support to 1.7, and the socket shutdown parts added by me.
@mrozigor what do you think?
from crow.
If this isn't really necessary then I think that this is waste of time.
from crow.
closing this for now, @choice17 feel free to reopen if this issue is really important
from crow.
Related Issues (20)
- Websocket Question HOT 4
- How can i know the progress of one post request? HOT 2
- Easily produced 'Worker Crash' with many simple concurrent http requests
- debian package is missing from the release section of version 1.1.0
- Please add new released version 1.1.0 to vcpkg HOT 1
- Compiler-Warning: ISO C++11 requires whitespace after the macro name
- How to use Middleware with CROW Blueprint HOT 13
- Websocket with dynamic routes in 1.1.0 HOT 1
- Update master to Conan 1.1.0 HOT 6
- Undocummented Macros HOT 2
- Mustache rendering adding extra quotes HOT 1
- Crow_enable_ssl HOT 1
- Crow Authorization Headers not working with CORs HOT 2
- Crow async usability HOT 2
- Troubles with crow running with apache2
- Cookie work cases HOT 1
- Websocket random generator - while loop HOT 4
- Error in installation HOT 4
- Is the Crow framework production-ready? I mean if I combine it with additional libraries, will it be ok for production? HOT 3
- Is it ok to use `#pragma once` instead of `#define CROW_STUFF_H` in crow's header files? HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from crow.