Better proxy support available via libcurl?

[Werner Koch]

On Fri,  4 Aug 2006 11:36, Christoph Ludwig said:

> Sorry to intrude - are there any online resources that summarize these
> discussions? And that give some guidelines what does (according to the FSF)
> constitute an effective "license barrier" between two applications. (As soon
> as they communicate over the network? As soon as they communicate over a
> standard protocoll like http? ...)

The GPL FAQ has some answers for you.  For example
http://www.gnu.org/licenses/gpl-faq.html#MereAggregation says:

  What constitutes combining two parts into one program? This is a
  legal question, which ultimately judges will decide. We believe that
  a proper criterion depends both on the mechanism of communication
  (exec, pipes, rpc, function calls within a shared address space,
  etc.) and the semantics of the communication (what kinds of
  information are interchanged).

  If the modules are included in the same executable file, they are
  definitely combined in one program. If modules are designed to run
  linked together in a shared address space, that almost surely means
  combining them into one program.

  By contrast, pipes, sockets and command-line arguments are
  communication mechanisms normally used between two separate
  programs. So when they are used for communication, the modules
  normally are separate programs. But if the semantics of the
  communication are intimate enough, exchanging complex internal data
  structures, that too could be a basis to consider the two parts as
  combined into a larger program.



Salam-Shalom,

   Werner