You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
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.
The text was updated successfully, but these errors were encountered: