Skip to content

Conversation

enriquedacostacambio
Copy link

Just that.

Usage:

git clone git://github.com/enriquedacostacambio/LittleProxy.git
cd LittleProxy
./run.bash --port 8000 --username user --password pass

@@ -0,0 +1,31 @@
package org.littleshoot.proxy.impl;

Choose a reason for hiding this comment

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

not sure about this package.

@ganskef
Copy link
Collaborator

ganskef commented Apr 12, 2016

Hi @enriquedacostacambio: First of all, thank you for your contribution!

Personally I think the Launcher class should be a small example. I see the intention of LP as a framework and the concrete application should have to define its requirements in a Launcher. I'm unhappy too with the huge grown connection classes with its inherited design. A lot of parameters and modes. I'm dreaming of a loose coupled design like the pipeline/handler concept in Netty.

@jekh: Any thoughts about hat?

@enriquedacostacambio
Copy link
Author

Hi @ganskef thanks for the reply!

I understand your point, it makes sense. I guess i'm looking at it from my own use case perspective. I'm using the LP as a tool for testing in development (and qa) boxes, to make sure my app works well with proxies, but I don't deploy any proxy in the actual environment myself.

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.

2 participants