RE: [GD-Windows] Process communication

[Jon W. <hp...@mi...>]

>     I'll look at DCOM. I'm not so much interested in managing multiple
> resources or versioning, we find Sourcesafe adequate for that. I'm more

To each his own, I guess :-)

> interested in developing a single monolihic (.wad) style file format
> Gigabytes large containing all final/production binary assets of the game.

You might want to make part of your build process be to re-generate
the wad file(s) from sources, with actual dependency maps. That way,
you have full control of what goes into it, and it's never fragmented
or out of date. You could do it on each client as part of make; the
only cost is extra disk space and sync time. Of course, with SourceSafe,
that might become a problem.

>     This isn't a massive versioning exercise - all I want is a
> high capacity
> pipe between myself and another application on another machine on our
> intranet.

I see. Basically, the remote-ness only comes into play in the development
environment, and it's there because you want one master machine that
stores and keeps assets, rather than having the assets and file building
go through source control to the clients.

Anything works, there. You might consider just banging something out with
raw sockets. Or you could use Apache with a plug-in and wrap it all in
HTTP. Or you could use network mounts and proper file locking. I'd prefer
either of these solutions to having to write and use something RPC-like
(such as DCOM). Yes, I'm no great RPC fan :-)

Cheers,

			/ h+