Skip to content

s,cppnetlib,network, #372

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 30, 2014
Merged

s,cppnetlib,network, #372

merged 1 commit into from
Jan 30, 2014

Conversation

ruslo
Copy link

@ruslo ruslo commented Jan 24, 2014

No description provided.

@ruslo
Copy link
Author

ruslo commented Jan 24, 2014

Probably now variables need to be renamed from CPP-NETLIB_ to NETWORK_? (:

@deanberris
Copy link
Member

I would hold off on the CMAKE variables -- I think there's value in the project name being there at least. ;)

@@ -8,11 +8,11 @@
cmake_minimum_required(VERSION 2.8)
project(CPP-NETLIB)

option( CPP-NETLIB_BUILD_SHARED_LIBS "Build cpp-netlib as shared libraries." OFF )
option( CPP-NETLIB_BUILD_SINGLE_LIB "Build cpp-netlib into a single library" OFF )
option( CPP-NETLIB_BUILD_SHARED_LIBS "Build network as shared libraries." OFF )
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Haha -- I think you did too thorough a sed script here. ;)

You'd want to keep cpp-netlib in these comments (and other places where it's descriptive rather than "normative"). 😁

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did it on purpose. It depends on how to name main library.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Though it's better to quote this name. This looks weird: Build the examples using network. (:

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I still would like to keep cpp-netlib here instead. These are descriptions, which really should be geared towards humans. :)

That said, I think having the actual name of the output binary is a good idea. In which case something like:

"Build cpp-netlib shared libraries (network-.so or network-.dll)."

@glynos
Copy link
Member

glynos commented Jan 24, 2014

In fact it isn't really necessary to change the prefix for what will be deprecated and removed anyway, as new stuff is developed. Eventually all the code that will replace these libraries ought to come with the network prefix. This is so we can have the old and new stuff being able to run side-by-side as we move to 1.0.

@ruslo
Copy link
Author

ruslo commented Jan 24, 2014

I'm a little bit confused...

To summarize, expected:

project(CPP-NETLIB)
option(CPP-NETLIB_* "... cpp-netlib ...")
add_library(network-* ${CPP-NETLIB_*_SRCS})
add_library(cppnetlib ... ${CPP-NETLIB_*_SRCS})

If single library will build output: cppnetlib
If not single: network-uri, network-client, network-server
?

@deanberris
Copy link
Member

I think you got the gist of what I'd like to happen @ruslo :)

Single library output: cppnetlib
Individual libraries: network-*

I also agree with @glynos but I'd rather be migrating the names now and cutting them out aggressively in the coming days/weeks. This means, all the deprecated stuff (message framework, etc) will fall by the wayside and won't be developed anymore -- and actually removed from the codebase.

@@ -8,14 +8,14 @@ include_directories(${CPP-NETLIB_SOURCE_DIR}/concurrency/src
${CPP-NETLIB_SOURCE_DIR}
)
if (CPP-NETLIB_BUILD_TESTS)
add_executable(cpp-netlib-thread_pool_test thread_pool_test.cpp)
target_link_libraries(cpp-netlib-thread_pool_test
add_executable(network-thread_pool_test thread_pool_test.cpp)
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about test executable? Revert it too?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes please, thanks @ruslo :)

@ruslo
Copy link
Author

ruslo commented Jan 26, 2014

Libraries list:

network-constants
network-http-message
network-http-message-wrappers
network-http-server
network-http-v2-client
network-logging
network-message
network-message-directives
network-message-wrappers
network-uri
network_concurrency
network_error

@ruslo
Copy link
Author

ruslo commented Jan 26, 2014

I can't find travis build. Are you sure cpp-netlib is activated?
See this link: http://docs.travis-ci.com/user/getting-started/

@glynos
Copy link
Member

glynos commented Jan 26, 2014

At least it's working here:

https://travis-ci.org/glynos/cpp-netlib

I'll see what I can do set it up for the cpp-netlib repo.

@deanberris
Copy link
Member

@ruslo -- can you please rebase/merge from HEAD, so we can merge this soon? Thanks.

@ruslo
Copy link
Author

ruslo commented Jan 28, 2014

@ruslo -- can you please rebase/merge from HEAD, so we can merge this soon? Thanks.

Ready to merge:
https://github.com/ruslo/cpp-netlib/commit/19cc4d09f992609c058b2e2f93694d3d92a15823

@deanberris
Copy link
Member

Thanks @ruslo -- sorry for the delay.

LGTM

deanberris added a commit that referenced this pull request Jan 30, 2014
@deanberris deanberris merged commit d85820e into cpp-netlib:master Jan 30, 2014
@ruslo
Copy link
Author

ruslo commented Jan 30, 2014

Thanks, Dean!

Libraries list's current state:

network-constants
network-http-message
network-http-message-wrappers
network-http-server
network-http-v2-client
network-logging
network-message
network-message-directives
network-message-wrappers
network-uri
network_concurrency
network_error

What is the next step?

@ruslo
Copy link
Author

ruslo commented Jan 30, 2014

At least it's working here:
https://travis-ci.org/glynos/cpp-netlib
I'll see what I can do set it up for the cpp-netlib repo.

@deanberris @glynos Yep, my repo working too: https://travis-ci.org/ruslo/cpp-netlib
And uri repo of cpp-netlib organization: https://travis-ci.org/cpp-netlib/uri
but not cpp-netlib repo of cpp-netlib organization: https://travis-ci.org/cpp-netlib/cpp-netlib

@deanberris
Copy link
Member

Are network_concurrency and network_error typo's? It'd be great if we can make this consistent as network-concurrency and network-error.

Does anybody know how to make Travis work with cpp-netlib?

@glynos
Copy link
Member

glynos commented Jan 30, 2014

On 30 January 2014 09:19, Dean Michael Berris notifications@github.comwrote:

Are network_concurrency and network_error typo's? It'd be great if we can
make this consistent as network-concurrency and network-error.

Does anybody know how to make Travis work with cpp-netlib?

Yeah, it's not obvious, but I just triggered a build for this repo.

Reply to this email directly or view it on
GitHubhttps://github.com//pull/372#issuecomment-33667838

.

@deanberris
Copy link
Member

@glynos Huh. I think we may be clobbering settings on each other. 😀 I'll let you figure this out going forward. :)

@ruslo
Copy link
Author

ruslo commented Jan 30, 2014

Are network_concurrency and network_error typo's?

No

It'd be great if we can make this consistent as network-concurrency and network-error

@deanberris sure, I just think that if you want to remove/merge this libraries then there is no difference
what is the library name (:

I'll open new PR if you don't mind. This PR becomes a little bit messy.

@glynos
Copy link
Member

glynos commented Jan 30, 2014

On 30 January 2014 08:41, Ruslan Baratov notifications@github.com wrote:

Thanks, Dean!

Libraries list's current state:

network-constants
network-http-message
network-http-message-wrappers
network-http-server
network-http-v2-client
network-logging
network-message
network-message-directives
network-message-wrappers
network-uri
network_concurrency
network_error

What is the next step?

The next step is to finish the HTTP client and HTTP server, before removing
the old libraries.

Glyn

@deanberris
Copy link
Member

@ruslo Yes, please send in a new PR. network-concurrency should be the correct name, and AFAIK it's not going away. If anything I'd like to implement the standards executor proposal.

network-error on the other hand is something worth keeping unless @glynos thinks otherwise.

@ruslo ruslo deleted the libnames-refactor branch January 30, 2014 08:36
@glynos
Copy link
Member

glynos commented Jan 30, 2014

I don't think it's worth keeping network-error over the long run. I intended it to be a specialization of std::system_error for this library but I no longer feel this is necessary, and it's not being used by the HTTP v2 client.

@ruslo
Copy link
Author

ruslo commented Jan 30, 2014

@ruslo
Copy link
Author

ruslo commented Jan 30, 2014

The next step is to finish the HTTP client and HTTP server, before removing the old libraries.

What part is unfinished C++ or CMake?

@glynos
Copy link
Member

glynos commented Jan 30, 2014

None, for the time-being.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants