[Openmcl-devel] AWS API code (re: GUI:BACKGROUND-PROCESS-RUN-FUNCTION)
rpgoldman at sift.info
Wed Jan 25 19:15:09 UTC 2012
On 1/25/12 Jan 25 -1:01 PM, Ron Garret wrote:
> BTW and FYI, the reason I'm using GUI:BACKGROUND-PROCESS-RUN-FUNCTION is that I'm writing some code to interface to Amazon's AWS API. Spinning up instances takes a while, so I do them in parallel to save time. I'm running CCL eval servers on the instances, so I essentially have a Lisp supercomputer that I can spin up whenever I need it. It's pretty wizzy, if I do say so myself :-)
> If anyone is interested in this code let me know and I'll make it available. Also, if you're in the Bay Area, I'm going to be presenting it at the BALispers meetup this weekend.
I'd be interested. I have been using Amazon's EC2 for a bunch of
things, some lisp and some not. But so far I have been using perl to
handle the launching and job management: the absence of a common
RUN-SHELL-COMMAND, and FORK, among other things, make it almost
impossible to use portable CL for such scripting.
> On Jan 25, 2012, at 10:54 AM, Ron Garret wrote:
>> Lovely! Thank you!
>> On Jan 25, 2012, at 10:10 AM, Gail Zacharias wrote:
>>> Should be fixed now.
>>> On Wed, Jan 25, 2012 at 6:32 AM, Gail Zacharias <gz at clozure.com> wrote:
>>> I've been making changes in that area, looks like I broke something I'll look into it.
>>> On Jan 25, 2012, at 4:32 AM, Ron Garret <ron at flownet.com> wrote:
>>>> It's not documented, but it works in the app store version, not in the trunk. In the app store version it works like process-run-funciton except that if the thread produces output it pops up a background listener window instead of dumping it to the altconsole. In the trunk I get this error immediately, even if the thread produces no output:
>>>>> Error: Slot GUI::WINDOW is unbound in #<BACKGROUND-COCOA-LISTENER-PROCESS foo(304) [Active] #x30200361C7BD>
>>>>> While executing: #<CCL::STANDARD-KERNEL-METHOD SLOT-UNBOUND (T T T)>, in process foo(304).
>>>> Is this supposed to work? Should I file a ticket?
>>>> Openmcl-devel mailing list
>>>> Openmcl-devel at clozure.com
>> Openmcl-devel mailing list
>> Openmcl-devel at clozure.com
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
More information about the Openmcl-devel