Skip to content
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

Components: Specialised vs General #6

Open
Idrinth opened this issue Sep 17, 2016 · 2 comments
Open

Components: Specialised vs General #6

Idrinth opened this issue Sep 17, 2016 · 2 comments
Assignees

Comments

@Idrinth
Copy link
Member

Idrinth commented Sep 17, 2016

I'm wondering if we should try to provide generally useful components first and then an adjustment to make them work well with the structure discussed here or if we should specialize them from the start.

@Maurice-Betzel
Copy link
Contributor

I am letting my thoughts run freely and sort it out later to discover the gaps.
But it is good to specify the patterns needed seperatly and then discuss the solutions.

@Idrinth
Copy link
Member Author

Idrinth commented Sep 18, 2016

Just as an example, I can make the php session general, accepting any kind of serialization function, so that people in need of let's say xml could use it as well, while on the other hand I could hardcode a serialization via thrift there and enforce it's usage.

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

No branches or pull requests

2 participants