[Pipet Devel] http protocol

[Brad Chapman]

> Well, you just hit on something I knew we would have to deal with.  
The 
>script 'loci' in the root directory should be a command-line program 
that
>launches the fronts and middle as separate processes.  Right now, it 
has 
>some Gnome stuff in it, which it should NOT.  This is a left-over 
from 
>before our change in directory structure.
> 
> Don't worry about making the 'loci' script work right, Brad.  I want 
to add
> that to my personal TODO.

Okee dokee, I'm not going to complain! It's all you, baby.
 
> I wouldn't characterize Loci's brokerage of different communications
> protocols
> as being front-to-middle communication.

You're right, front-to-middle only on the same computer. Gotcha!

> Here's a flowchart:
[..snip..]

I *think* I am on the same page with you since my hand-drawn 
"Loci communications diagram" that I am trying to work off looks very 
similar to what you were diagramming, only a lot more ugly. We should 
try and make sure everyone is still in agreement on how things should 
go once we start to implement different protocols. For now, the 
front-to-middle communication is all I'm working on, and we'll have to 
worry about other stuff as it comes. 
    I just cvsed more of the changes towards complete separation 
between front and middle. The streaming dialog model is implemented 
for locus addition and connection, and all of the talking occurs 
through a port on the localhost, so from as far as I know security 
should not be a problem with this (unless someone already hacked your 
machine). There is a pretty weak communication log starting to be 
implemented, and the front now waits for a response from the middle, 
processes the response, and then does stuff with it (thanks for the 
Expect code--that was a big help!). This is just barely tested to 
work, and more will be coming (but after I spend some time with cactus 
and exams(ugh!)). 
    Hopefully all of my ugly code will be out of the front soon so 
that Jeff can work his magic on it!

>Plea: Guys, for the sake of simplicity (and security!) can we just 
deal with
>_one_ Internet connection (between middles)?  At least until we've 
got this
>stuff down to a science.  What do you say?

Definately! 100% with you!

>The 'INTERNET' connection is something we haven't discussed at all.  
It
>involves 2 middles talking to each other.  Of course it can be via 
standard
>Internet socket.  Some may argue for CORBA...I wouldn't ;-)

I'm going to definately agrue for corba pretty heavily on this, but I 
think we should focus on local stuff first before we move into this. 
There definately isn't enough infrastructure in the middle to deal 
with middle to middle communications effectively now, so this is 
something I'll work on. Then we can fight it out over this....

Brad