Responding to Users When the Response Isn’t Immediately Available
We head back to the Creators Portal application to put these messages to use. The individual video screen has two forms on it, one for naming the video and one for describing it. Why two forms? We don’t want to present users with an HTTP form sitting on top of a database table. They’re not here to edit a video—they’re here to name a video. This is an example of a task-based UI,[68] a UI geared toward achieving specific ends rather than raw editing.
That said, we’ll only cover naming the videos, since describing them is an exercise at the end of the chapter. The name appears in a text box that submits back to our server, ending up at the handleNameVideo handler:
Get Practical Microservices now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
