Re: [Ayttm-devel] Re: [Ayttm-commits] CVS: ayttm/modules/msn2/libmsn2 msn_bittybits.C,1.8,1.9

[Edward L. Haletky]

Hi Philip, Colin,

libproxy is linked into many of the modules.... As it maybe
linked into the core but it is not exported by the core.

Therefore AIM/ICQ (only ones with proxy support and frankly 
that is itself an issue) rely on libproxy to link properly.

We should only proxy http requests not the protocols as I
tried this in EB at one time and had to disable the proxy 
to make any of it work.

-Edward

On Tue, 2003-03-25 at 07:43, Philip S Tellis wrote:
> On 25 Mar 2003, Edward L. Haletky wrote:
> 
> > In libproxy someone added code to an interface that resides in ayttm/src
> > instead of ayttm/libproxy. This interface is exposed via tcp_utils.[ch].
> > It is the ay_socket_new_async interface. I think that libproxy should
> > NOT depend upon AYTTM in order to work. 
> 
> well, libproxy is really not a lib.  it's linked into the core at link 
> time.
> 
> > THere are several reasons for this but the main one is that proxy is
> > proxy. AYTTM is AYTTM and I do not think that we want an AYTTM
> > specific routine in a library used for other purposes. In addition
> > this really does break a number of items when you have a lower level
> > interface dependent upon a higher level one.
> 
> not sure i understand this.  that's the way service modules call 
> services in the core.  all service modules are dependent on interfaces 
> exported by the core.  libproxy shouldn't be dependent on how it should 
> do socket connects, only on what should go over those sockets.
> 
> socket implementations are different on different platforms, so need to 
> be handled elsewhere.
> 
> Philip