Brutally Roll Your Own Backend – Part 8

lamp-stack (1)

Brutally Roll Your Own is a video series on building a PUSH enabled mobile application from scratch, using a Linux, Apache, MySQL, PHP (LAMP) server for the back end, and Delphi for the mobile app. In Part-8 we flesh out that REST endpoint class and add an animation to our main form to indicate responsiveness during HTTP calls.
Remember that this is all unscripted and off the cuff!

Sign up with linode here

Sign up for Linode by clicking here!
If you select linode to host your back end, as I suggest in part 2 of this video series, please consider signing up through my referral link above. I host my servers (including this site) on linode, and this will help pay the bills! If you already have an account, you can enter this referral code: fb41cc68526abce4ffa14bfd797d5c4cc684f192  Your support is appreciated!

[Listing of all parts]

Print Friendly, PDF & Email

6 thoughts on “Brutally Roll Your Own Backend – Part 8”

  1. Thanks for this series. I’m a fairly novice programmer and the working with interfaces is particularly enlightening. That aside, just something I noticed when you mentioned problems with recording software. Part 8 video takes a lot of buffering, so I looked at the size of it and it’s 1GB ! for 49mins. That makes it upto 10x larger than any comparable length video you’ve produced. Maybe related to your software problem ?, maybe a significantly inadvertent increase in resolution ? Just a thought, if it helps. Cheers.

    • I’m pleased you’re enjoying the series. That is interesting, part-8 was rendered from a different machine than the others (because I had to be in the office the day it was edited). I may re-bake that one.

      The recording issue I finally figured out, the screen recorder shares the F9 keyboard shortcut with the RAD IDE, which explains both why it kept pausing the recording, and why my RAD Studio short-cut wasn’t working! *doh*

  2. Very informative, I learnt a lot. However, I’d like to point out that I’ve had issues with TTask on longer running tasks under iOS. I’m guessing that the main thread polls the TTask so much that the OS decides there’s a problem and cancels the app. In the crash log, iOS is nice enough to tell you “NON-FATAL CONDITION (this is NOT a crash)” but still ends the application, just in case! I’ve found that a plain old TThread is the way to go.

    • I’ve been trying to decide on the best time to post the sources for some time now.
      My concern has been that I am literally writing this code on-the-fly as I record the videos, and therefore it is still incomplete and subject to change over time.
      Having said this, you are not the first to ask for the source code, and so I will be moving it into my public repository shortly. Keep an eye out for Part-9.

Leave a Comment