Jump to content

Recommended Posts

Posted

What is HTML5 Web Storage?

 

With HTML5, web pages can store data locally within the user's browser.

 

Earlier, this was done with cookies. However, Web Storage is more secure and faster. The data is not included with every server request, but used ONLY when asked for. It is also possible to store large amounts of data, without affecting the website's performance.

 

The data is stored in key/value pairs, and a web page can only access data stored by itself.

Browser Support

 

 

Web storage is supported in Internet Explorer 8+, Firefox, Opera, Chrome, and Safari.

 

Note: Internet Explorer 7 and earlier versions, do not support web storage.

localStorage and sessionStorage

 

There are two new objects for storing data on the client:

 

    localStorage - stores data with no expiration date

    sessionStorage - stores data for one session

 

Before using web storage, check browser support for localStorage and sessionStorage:

if(typeof(Storage)!=="undefined")
  {
  // Yes! localStorage and sessionStorage support!
  // Some code.....
  }
else
  {
  // Sorry! No web storage support..
  }

 

The localStorage Object

 

The localStorage object stores the data with no expiration date. The data will not be deleted when the browser is closed, and will be available the next day, week, or year.

localStorage.lastname="Smith";
document.getElementById("result").innerHTML="Last name: "
+ localStorage.lastname; 

 

Example explained:

 

    Create a localStorage key/value pair with key="lastname" and value="Smith"

    Retrieve the value of the "lastname" key and insert it into the element with id="result"

 

Tip: Key/value pairs are always stored as strings. Remember to convert them to another format when needed.

 

The following example counts the number of times a user has clicked a button. In this code the value string is converted to a number to be able to increase the counter:

if (localStorage.clickcount)
  {
  localStorage.clickcount=Number(localStorage.clickcount)+1;
  }
else
  {
  localStorage.clickcount=1;
  }
document.getElementById("result").innerHTML="You have clicked the button " + localStorage.clickcount + " time(s).";

 

The sessionStorage Object

 

The sessionStorage object is equal to the localStorage object, except that it stores the data for only one session. The data is deleted when the user closes the browser window.

 

The following example counts the number of times a user has clicked a button, in the current session:

if (sessionStorage.clickcount)
  {
  sessionStorage.clickcount=Number(sessionStorage.clickcount)+1;
  }
else
  {
  sessionStorage.clickcount=1;
  }
document.getElementById("result").innerHTML="You have clicked the button " + sessionStorage.clickcount + " time(s) in this session."; 

 

 

:happyforever: :happyforever: :happyforever:

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.



  • Posts

    • We are taking new orders. Kindly DM us on Telegram!
    • Hello everyone!  I’d like to share an experience that might serve as a lesson for anyone planning to work with third-party protection services—specifically, Active Anticheat. I know this might sound like a strange job request, but  our player base mostly consists of veteran of Lineage 2 players who are used to using bots as part of their gameplay experience. As server administrators, we decided to adapt to our users. That’s why we approached Active Anticheat with a proposal: Allow bot usage under certain conditions. We explained everything in detail, and they agreed.   📌 February – A Promising Start On February 16th, we contacted Active Anticheat to request a custom antibot system. The idea was to kick players using bots during specific times (like sieges), but allow them to log back in without bots afterward. After a few discussions, both sides agreed on the following solution: Bots allowed during regular days. During siege events, anyone using a bot would be automatically kicked. Kicked players could log back in without using bots. The deal was priced at $5,000, which we already paid on March 31st, 2025. Active Anticheat promised delivery by the end of April, or at the latest, by May. Screenshot:  Deal 1 Deal 2   🕐 May – The Delays Begin We followed up multiple times in May, only to finally hear back on May 26th: “It won’t be ready this month. But we’re working on a big update coming in June.” That update? Still nowhere to be seen, even as I’m writing this post. Screenshot:  Delayed   🔁 Plan B – L2Walker Rejected, Adrenaline Offered With our server launch schedule getting tighter, we needed an alternative. At the end of June, we asked Active Anticheat: “Can you at least allow L2Walker access to the server?” Their response on June 28th: “L2Walker can’t be allowed. But we can allow Adrenaline (free & paid version) and L2Helper for $2,000 + $300 (for a new license).” We agreed, hoping it would be a temporary fix while waiting for the promised “big update” (which we had already paid $5,000 for, remember?). Screenshot:  New Offer 1 New Offer 2 New Offer 3   ❌ AA Failed Their setup took about a week. We ran 2–3 rounds of testing using clean clients. The result? Adrenaline (both free and paid) couldn’t connect to our server. It couldn’t detect the Lineage 2 client, because the custom Active Anticheat protection was blocking it. We reached out to Active Anticheat for support, and their response? “You should contact Adrenaline support to enable free Adrenaline for your server. Adrenaline blocks it by default when Active Anticheat is detected.” Then we tested Premium Adrenaline. And it still didn’t work. Active Anticheat stood firm: “It’s not our fault. Adrenaline blocked us—not the other way around.” Screenshot: Failed 1 Failed 2   💸 The Bitter Reality Today, we’re still waiting for answers. No reply. No fix. No update. No refund. We’ve spent a total of $7,300 and received nothing functional in return. And this, despite their full agreement with our initial plan.  
  • Topics

×
×
  • Create New...

AdBlock Extension Detected!

Our website is made possible by displaying online advertisements to our members.

Please disable AdBlock browser extension first, to be able to use our community.

I've Disabled AdBlock