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

Request/Response #723

Open
sandeepone opened this issue Apr 26, 2014 · 1 comment
Open

Request/Response #723

sandeepone opened this issue Apr 26, 2014 · 1 comment

Comments

@sandeepone
Copy link
Member

IMHO we should replace the existing request/response with the symfony httpfoundation.
https://github.com/symfony/symfony/tree/master/src/Symfony/Component/HttpFoundation

We can extend and replace the present request/response with the above class. I'm still open to opinions on various other approaches used in slim and other micro frameworks.

@sergeyklay
Copy link
Contributor

Yes, I agree with you \o/

I would like to try (first) use Gleez Autoloader in Codebench and if it will show their best side to use it everywhere. Including for Request/Response, etc.

But I would like to express my opinion about Request/Response. You understand that this is a large amount of work? Let us first transform our classes to namespaces. Let's create a new branch for this. Current feature-bootstrap-3 branch can be a master. Current master may be old-stable. New version we can bump to 1.0.0

I believe that in order so that we could use all sorts of things from Symphony (Zend, Laravel, Fuel, Yii, Aura, Nette, Ohanzee, etc,) we must use PSR-0/1/2/3/4

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