Re: Node and callback hell - Promises -- WEB400

Subject: Re: Node and callback hell - Promises
From: Nathan Andelin <nandelin@xxxxxxxxx>
Date: Fri, 23 Oct 2015 14:31:25 -0600
List-archive: <http://archive.midrange.com/web400/>
List-help: <mailto:web400-request@midrange.com?subject=help>
List-id: "Web Enabling the IBM i \(AS/400 and iSeries\)" <web400.midrange.com>
List-post: <mailto:web400@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/web400>, <mailto:web400-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/web400>, <mailto:web400-request@midrange.com?subject=unsubscribe>

Thanks for the explanation, Keven; If your application is doing nested
record retrieval, then you you may end up coding nested call-backs, which
could become rather deep. So you're still in "hell", but "promises" makes
the syntax a bit more palatable.

Why not just "call" an RPG program to handle nested record retrieval, as
opposed to coding nested call-backs in Node.js?

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Node and callback hell - Promises , Kevin Turner

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.