[Openmcl-devel] OpenMCL / Cocoa

Samantha Atkins sjatkins at mac.com
Tue Jan 24 12:00:10 PST 2006

It is not a bad idea at all.  GUI's interact with their data/ 
computational models relatively slowly.  Sockets should be more than  
fast enough to handle this traffic, especially on the same box.  App  
to database traffic commonly goes over a socket (often not even on  
the same box) and that is much higher bandwidth than you need to  
support your separate process GUI.

- samantha

On Jan 24, 2006, at 10:47 AM, Gary King wrote:

> I know that progress continues with the Objective C / Cocoa bridge
> but I'm wondering if anyone has worked on running OpenMCL and a Cocoa
> application using sockets to communicate between them. I have some
> ideas I'd like to play with where the GUI could be Cocoa and some of
> the smarts could be OpenMCL. I think that sockets would be fast
> enough, etc. to handle simple needs. Unfortunately, I'm pressed for
> time and would rather not much with setup unless I have to so...
> Has anyone else build any infrastructure along these lines that
> they'd like to share? Also, is this a _bad_ idea? Am I missing
> something?
> Thanks,
> -- 
> Gary Warren King
> metabang.com
> http://www.metabang.com/
> _______________________________________________
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
> http://clozure.com/mailman/listinfo/openmcl-devel

More information about the Openmcl-devel mailing list