Managing State

By Ashwin Venugopal -

 




Storing Data On Server Side

There are numerous methods available for storing data on the server. It's important to keep in mind that Blazor WebAssembly will always require an API. In contrast, Blazor Server can access server-side resources directly without needing an API.

If you're developing a Blazor Server application and don't want to switch to Blazor WebAssembly, you should choose direct access. We can initially utilize direct server access and transition to an API later if we choose to. In terms of data storage options, we have the ability to store data in Blob storage, key-value storage, a relational database, or table storage. The options are virtually limitless. As long as .NET can interact with the technology, we can implement it.

Storing Data In URL

Data, in this case, could refer to the ID of the blog post or the specific page number when pagination is being utilized. To read a parameter from the URL, we can use the following syntax-

@page "/post/{BlogPostId:int}"

The URL is post followed by Id of the post. To find that particular route, BlogPostId must be an integer, otherwise the route won't be found. We will also need a public parameter with the same name.

When storing data in the URL, it's important to utilize the OnParametersSet or OnParametersSetAsync methods; otherwise, the data will not refresh if the parameter changes. If a parameter is modified, Blazor does not execute OnInitializedAsync again.

Hence, our post.razor component fetches the items that vary depending on the URL parameter in OnParametersSet, while it retrieves the elements that remain constant regardless of the parameter in OnInitializedAsync. We can also use optional parameters by specifying them as nullable like this-

@page "/post/{BlogPostId:int?}"

Route Constraints

When we define the type for a parameter, this is referred to as a route constraint. We introduce a constraint so that the match will occur only if the parameter value can be transformed into the type we've indicated. The constraints listed below are available:

• bool

• datetime

• decimal

• float

• guid

• int

• long

The components of the URL will be transformed into a CLR object. Hence, it's crucial to apply an invariant culture when incorporating them into a URL.

Using A Query String

We can also read data from the query string. NavigationManager gives us access to the URI, so by using this code, we can access the query string parameters-

@inject NavigationManager Navigation

@code{

var query = new Uri(Navigation.Uri).Query;

}

Conclusion

We have successfully learnt about various methods of storing data.


Comments

Post a Comment

Popular posts from this blog

Information Protection Scanner: Resolve Issues with Information Protection Scanner Deployment

By Ashwin Venugopal -
Image
  About If you are experiencing problems with the Microsoft Purview Information Protection scanner, check the health of your deployment by utilizing the Start-ScannerDiagnosticsPowerShell cmdlet to start the scanner diagnostic tool. The diagnostics tool checks the following details and then creates a log files with the results: Whether the database is up to date. Whether network URLs are accessible. Whether there's a valid authentication token and policy can be acquired. Whether the profile is defined in the Azure portal. Whether offline/online configuration exists and can be acquired. Whether the rules configured are valid.  The Start-ScannerDiagnostics command does not perform a comprehensive check of prerequisites. If you encounter problems with the scanner, you need to verify that your system meets the scanner's requirements, and that your scanner's configuration and installation are finished.  Verify Scanning Details Per Scanner Node and Repository Run the Get-ScanSt...
Read more

How AMI Store & Restore Works?

By Ashwin Venugopal -
Image
  CreateStoreImageTask The CreateStoreImageTask API stores an AMI as a single object in an S3 bucket. The API initiates a task that collects all the data from the AMI and its associated snapshots, subsequently using an S3 multipart upload to store this data in an S3 object. It gathers all elements of the AMI, including most of the non-Region-specific metadata and all EBS snapshots included in the AMI, and consolidates them into a single object in S3. During the upload process, the data is compressed to minimize the space utilized in S3, which means that the S3 object could be smaller than the total sizes of the snapshots in the AMI. If the account making this API call has access to AMI and snapshot tags, they will be retained. The S3 object shares the same ID as the AMI, except it has a .bin extension. Additionally, the S3 metadata tags for the object include the AMI name, AMI description, AMI registration date, AMI owner account, and a timestamp indicating when the store operation...
Read more

Create A Store Image Task

By Ashwin Venugopal -
Image
  Introduction When you save an AMI in an S3 bucket, a task for storing the image is initiated. This store image task allows you to track the progress and result of the procedure. Securing your AMIs It is crucial to verify that the S3 bucket is set up with adequate security to protect the content of the AMI and that this security is upheld for the entire duration that the AMI objects are stored in the bucket. If this cannot be achieved, it is advisable to refrain from using these APIs. Make sure that public access to the S3 bucket is prohibited. It is suggested to activate Server-side encryption for the S3 buckets where you keep the AMIs, even though it’s not mandatory. When AMI snapshots are transferred to the S3 object, they are sent over TLS connections. It is possible to save AMIs that contain encrypted snapshots; however, the snapshots will be decrypted during the storing process. Identify the source AMI used to create a new Amazon EC2 AMI You can determine the AMI that was us...
Read more