329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
|
run-id)
(vector header res)))
;; BB> bb opinion - want to push responsibility into api (encapsulation), like waiting if db is busy and finding the db handle in the first place. why should the caller need to be concerned?? If my opinion carries, we'll remove the bb- and make other needful adjustments.
(define (bb-mdb-inserter mdb-expecting-proc mdbless-args)
(let ((mdb (db:delay-if-busy (tasks:open-db))))
(apply mdb-expecting-proc (cons mdb args))))
(define (tasks:bb-get-server-info . args)
(bb-mdb-inserter tasks:get-server-info args))
(define (tasks:bb-num-in-available-state . args)
(bb-mdb-inserter tasks:num-in-available-state args))
|
|
|
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
|
run-id)
(vector header res)))
;; BB> bb opinion - want to push responsibility into api (encapsulation), like waiting if db is busy and finding the db handle in the first place. why should the caller need to be concerned?? If my opinion carries, we'll remove the bb- and make other needful adjustments.
(define (bb-mdb-inserter mdb-expecting-proc mdbless-args)
(let ((mdb (db:delay-if-busy (tasks:open-db))))
(apply mdb-expecting-proc (cons mdb mdbless-args))))
(define (tasks:bb-get-server-info . args)
(bb-mdb-inserter tasks:get-server-info args))
(define (tasks:bb-num-in-available-state . args)
(bb-mdb-inserter tasks:num-in-available-state args))
|