I thought of that problem with firewall software, actually. But anyone who's really, really concerned about it to the point where they might consider blocking the communication would hopefully recognize 127.0.0.1 or whatever as the loopback address. Of course, using any of our fan-made AGI software also requires a bit of faith in the authors not to be doing stuff they shouldn't be doing. I agree that it is an issue, though.
The problem with DDE is I think that it's Windows-specific, and it requires broadcasting messages to all the programs running in Windows to get the communication started. I think we should design the communication protocol so that Linux, etc. users aren't left out of the possibility of utility integration.
I think Nick's got it right. If we want to be portable, we're probably going to have to use either pipes or sockets. Where each of them stands is pretty much like this:
where "server side" refers to the utility application such as the BLG and "client side" refers to the application that invokes the utility application, such as AGI Studio
sockets
the good:
- slightly less complicated than pipes on the client side; possibly less work for Nailhead

- Internet capable; whatever possible application that might have I don't know
- documentation is easy to find
- highly portable...the Windows Sockets API is designed to be compatible with the Berkeley Sockets API
the bad:
- slightly more complicated than pipes on the server side; may prevent novice programmers from developing integration capable AGI utilities
- could trigger firewalls; might make some people suspicious...might be a security hole
Pipes:
the good:
- very easy to use on the server side
- no triggering of firewalls
the bad:
- not so easy on the client side; I got it to work but I only understand what it's doing in an intuitive way; the MSDN example code is not completely clear
- no Internet capability - in order to be compatible with Windows 95, 98 and Me, we have to use unnamed pipes, which can't be created across a network connection
- documentation is not as easy to find
- less portable when doing things the MSDN example code way -- althought Unix may support pipes, it wouldn't set them up the same way the MSDN example code did