If a procedural APi is built on top of XgridFoundation, the
implementation of that APi will still need to do the "fragile" task
of managing an NSRunLoop by hand. So it seems like this approach
wouldn't result in anything more robust that what we already have
(in xgf for example).
But obviously, a procedural API that is built on top of the BEEP
layer would probably need to come from within Apple (unless someone
wants to reverse engineer the BEEP layer). That would mean the
benefits of points i), ii) and iv) are lost.
As you note, we don't have a public BEEP API, or a C API. However, if
we did either of those, we'd almost certainly use CFNetwork, which
means using CFRunLoop -- which probably isn't any better for you than
NSRunLoop. :-)
It sounds like the "hard" problem is mapping a call-back API onto a
RunLoop API. While tricky, hopefully it would be easier to do that
in C than its been for you to do in Python.
I wonder -- do any of the DRMAA folks have experience with that problem?
-- Ernie P.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xgrid-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xgrid-users/email@hidden
