Last post Oct 03, 2010 01:56 PM by ignatandrei
Oct 02, 2010 09:18 PM|BatmanBond3D|LINK
I am currently working on a site where I expect most of the visitors to be returning visitors. Their main use for this site will be to check a vast amount of data which should only occur some minor changes about once a day. I will expect quite a lot of
users and I would like my website to operate as efficiently as possible.
To make the site as efficient as possible I am thinking of building my website in a way that does not seem to be the way most web developers go about building their site I and would like to know what some of you think about my approach. I decided to make
query to the web server will require that session id to be sent to validate if the user is allowed to access that data or not. Also since the pages are HTML pages with the extension .html and do not change, even the pages themselves can be cached on the client.
As you can tell this site is going to be largely client based and I was wondering if this is a good approach to building a website or if I am going to run into troubles later on.
Oct 03, 2010 12:33 AM|Yawer Iqbal|LINK
Oct 03, 2010 10:31 AM|ignatandrei|LINK
All data relative to the user will be stored in cookies
Oh, yes. Let's say the REGISTERED user have some data from the site( favorites, emails, do not know what information your site provides) ... and, for some reasons, he has lost his cookies ( format PC, clear browser cache, ? ) or he tries to access the
site from another PC (work, internet cafe, and so on) .
Oct 03, 2010 11:45 AM|BatmanBond3D|LINK
If the user lost his cookies or logs in from another computer I will simply resend all the relevant data for that user. Again please consider that most of my users will be frequent users who will visit the site on average about once every two days. I would
estimate the total amount of data that will need to be sent to one user on the first page request in which no cookies have currently been created would be 3 mb at most and the size of changes to the data after the first page request will be in the order of 10
kb a day. For most of the pages all of this Data will be needed to render the page as I would like my pages to be very interactive. One problem I am worried about is if the cookies become corrupt for whatever reason and then the web page will constantly
be displaying incorrect data. One idea I have to solve this problem is to write a hash function that takes in the entire data related to that user and outputs a number. This hash will not need the entire data to compute what the value of the hash function
is. All it will need is the previous hash value and all the changes of the data.
If you don't agree with some things that I am saying please feel free to comment.
Oct 03, 2010 01:56 PM|ignatandrei|LINK
If the user lost his cookies or logs in from another computer I will simply resend all the relevant data for that user.
So you do not store only on cookies, but also on server side. Ok, then!