-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Move Fastcgi client implementation to its own package #4378
Comments
Sure, that's not a bad idea; but before that happens, the implementation needs to be rewritten: #3803 I would not recommend other applications using the implementation as-is. |
Interesting, I struggled to find a implementation to begin with really but I've looked at the others mentioned there on that issue. I will take a closer look although not sure gopher skills can help exactly here 😃 |
FWIW, @WeidiDeng has rewritten the It's not really an action item on my list, but if someone else wants to take this up, that's great too. |
Hi @mholt, I helped with this issue by opening a PR #6465. The goal was to carefully extract the client logic into a separate package, for readability and reusability. Let me know what you think! |
Oh wow, thank you! I will take a look soon :) |
Hi,
I've been looking for a client fastcgi implementation in Golang and the one is Caddy seems very feature rich, however although the
client.go
is using only the standard library thefastcgi.go
andcaddyfile.go
are using alot of other things.Would it be acceptable to move the pure fastcgi implementation which is designed around http://www.mit.edu/~yandros/doc/specs/fcgi-spec.html into its own package to allow easier consumption with other libraries and applications? I assume the implementation at this point is "completed" given there has never been any real movement I wonder if that would be acceptable to have it away from Caddy's development and just sit standalone?
Thanks in advance.
The text was updated successfully, but these errors were encountered: