Re: Node and callback hell - Promises

Yes well there are lots of better ways to code that example without promises - I just used that to illustrate the theory. The nested callbacks may have nothing to do with database interaction of course.

Sent from my iPad

On 23 Oct 2015, at 21:31, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

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?
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.


___________________________________________
This email has been scanned by iomartcloud.
http://www.iomartcloud.com/

________________________________

NOTICE: The information in this electronic mail transmission is intended by CoralTree Systems Ltd for the use of the named individuals or entity to which it is directed and may contain information that is privileged or otherwise confidential. If you have received this electronic mail transmission in error, please delete it from your system without copying or forwarding it, and notify the sender of the error by reply email or by telephone, so that the sender's address records can be corrected.



--------------------------------------------------------------------------------


CoralTree Systems Limited
25 Barnes Wallis Road
Segensworth East, Fareham
PO15 5TT

Company Registration Number 5021022.
Registered Office:
12-14 Carlton Place
Southampton, UK
SO15 2EA
VAT Registration Number 834 1020 74.