ticketing | Railway Station Ticketing System Based on JavaWeb

You say your Request agent that flows through the process flow has a number of Agents in it, but these don't need to be agents, they can be pure Java classes or requests can also simply carry a number of users to create.

It all depends on the granularity you require

To answer your question you can access the inside of the agents that travels through the process flow and use that to determine the delay or the number of resources to be seized as follow:

Just be sure that the Agent type in the advanced setting is set to the Agent type that you expect in this block. If you set the Source to create a specific agent type it will automatically update all the serially connected blocks for you.

Please note if the user creation process will vary for each user to be created you need a separate delay for each user... and thus it would be better to split into multiple agents for each user creation, and then have them seize, delay and release each resource separately.

With your current logic, they will all be seized and released at the same time.

From your endpoint in your script, I thought that you might have wanted to use "Batch update". Ref If my understanding is correct, the following sample curl in the official document can be used. Ref

I wouldn't lock the table at all, no need for. I think. When I have 500 tickets, I would create 500 records (tickets). When someone buys a numbers of tickets, you have to update these tickets as SOLD. Use a SELECT FOR UPDATE statement in combination with SKIP LOCKED to get the number of tickets you need and then UPDATE these selected records. Multiple customers can buy tickets at the same time, without issues.

The only thing left, is what to do when someone wants to buy 10 tickets when you don't have 10 tickets anymore.

I had to install the Microsoft OLE DB Driver for SQL Server and than it worked. Thanks for Hans Passant for pointing me in the right direction.

Couldn't think of a cleaner way to get the structure you want and had to manually loop through the different groupby levels adding one row at a time

You can't. You will need to store your "integer" as a String object and convert it as you need to perform you BigInteger operations.

Here's the issue.

You load the page and render the form. Then you choose an object representing a row of data with which to populate the form. At this point the form is already rendered.

You have two options:

1. Restructure your workflow so that the choice field and the edit form are on separate page loads. You load the dropdown field, choose an object, and submit the form, which then re-renders the form (200 on POST or redirect) with the data populated.

2. Handle the data through JavaScript on the client side. You will need to watch the dropdown field and then populate the form with data through JavaScript.

   A. You can either pass ALL of the data for all of the choices to the JavaScript on the initial page load, which could be a lot of data for a large table, or...

   B. You can retrieve the data through an API when the dropdown is changed.

I would favour the first option. Present the user with the dropdown and a next button (/edit/). Use that form data to redirect to a page with the edit form and a save button (/edit//). Use that form data to update the object and redirect back to the dropdown page (/edit/).

I advise you to follow many good techniques when developing a responsive webpage, here I explain to you:

• Replacing in your CSS absolute units such as px for percentages or em. It is always much better to work with relative measurements rather than absolute ones. From my experience, I always try to work with em, here is a conversion from px to em.
• Using responsive layouts like flex or grid.
• Adding metadata related to the viewport in the HTML head tag. I can see you haven't written it. As we can read in W3Schools viewport is the user's visible area of a web page. It varies with the device so it will be smaller on a mobile phone than on a computer screen. You should include the following element in all your web pages:

In conclusion, try to avoid absolute positioning because it is not the best option. Try to follow this advice and I am sure your webpage will turn so much better. :D.

Based on your sample data you can probably do this with an outer join