Okay, this has to stop, all of you.
Dumitru, people are trying to help you, but they expect you to do some
research and experimentation by yourself. You are expecting them to give
you a pre-cooked solution to your exact problem. That's not how this works.
As far as I can remember, you are the first to ask for this exact mix of
technologies, so there will be some work required to plug them together.
Everyone, this is not the way to foster a friendly community. Everyone is a
newbie at some point in their lives, and being outright insulting to people
for not conforming to your expectations is not cool. Please try to keep it
courteous and friendly, and if you can't, don't post. That's not to say you
can't ask people to clarify their questions, do some research on their own,
and so forth, but there are polite ways of saying all those things.
Now, back to the topic: As far as I know, there are no documents like the
one you point out for Go. The various pieces are all there, however. As
someone pointed out earlier, it's mostly a question of creating a server
that uses the net/http/fcgi package, and then telling Apache where that
server is listening. The net/http/fcgi package will take care of the
details of FastCGI, and give you an interface that's almost identical to
net/http's. Write handlers as if it were a regular HTTP server, and
everything should work.
And, of course, when you get it working, I think we'd all love a tutorial
on how to set up FastCGI Go applications, in the same spirit as the Python
document you linked to. Good luck!
On Saturday, November 3, 2012 2:24:49 PM UTC-7, Dumitru Ungureanu wrote:
I'm sorry, to me you'll always be *Avram* Hărvănescu.