Or your website has been written poorly and doesn't carry USER ID when the user moves. M Audio Axiom AIR Mini MIDI keyboard Ver. Memory interface 128bit Memory bandwidth 192.03GB/s 4GB of dedicated GDDR6 video memory, shared system memory 16307MB PCi Express x16 Gen3. Total 12TB of four external WD drives for backup. + x2 WD BLACK 2TB internal SATA 7,200rpm hard drives.I for internal projects 1 for Library clips/sounds/music/stills./backup of working projects. Driver version 30.0.101.1994 with 32GB of 3200MHz Corsair DDR4 ram.ġ x 250GB SSD D: drive for C: drive backup 1 x 250GB SamSung Evo 970 drive for Operating System. Intel i9900K Coffee Lake 3.6 to 5.1GHz CPU with Intel UHD 630 Graphics. Page file space 4.75GB.Īsus ROG STRIX Z390-F Gaming motherboard Rev 1.xx with Supreme FX inboard audio using the S1220A code. Direct X 12.1 Bios version 1401 latest hardware updates for Western Digital hard drives. It won't really be a problem in a couple of days. For example, when I travel Amazon, I do not have to keep logging on when I review different items and return to previous pages.Įither Amazon and others are using pixie dust, or your site it poorly written.Įither way: Meh. If you are having to login on every page you move in order to do any of these activities, then either your browser cookie caching is turned off or, less likely, your web browser is failing to store the necessary cookie(s) required. The only time you need to login is when you are wanting to post, view any PMs or your profile. You must be referring to this forum site for which is available to the general public with there is no requirement to log in to view the forums. Do you know how may times I have had to log on to my account in the last 30 minutes as I move from page to page of your website. Magix's owners may want to drain as much money as quickly as possible, because I think Vegas Video and all the other Magix products are about to die very sad deaths.Īs I leave behind a perky little program name Vegas. I barely avoided getting an upgrade when I saw all the comments about Magix and how bad of a company it is.ĭo you know how may times I have had to log on to my account in the last 30 minutes as I move from page to page of your website. Now I am ashamed to know it or Magix, the company "supporting" it. We swore by it and promoted to everyone we knew. I honestly cannot understand why you'd spend money on a program just to lose the investment made.Īnd this video editors I spent 20 years using is about to be ripped from my PC and discarded as well. Products freeze up, support links lead not to support areas but to sales departments trying to get me to buy a newer version of a product which, by current discussions is just as buggy as previous versions. I see complaints against your technical support area not from years ago, but from days ago. But I also find it hard to understand why a company would buy a smart little program just to grind it into the dust. If the counter key doesn't exist, this activates load.I cannot believe after all these years I am leaving Vegas video. If you really need the old application to mantain real-time statistics, and want to use Redis, then you would have to change legacy code to access it.Īt every hit, you can check thread's counter in Redis. Is it a huge no-no to do a redis call in a loop like I'm suggesting? Is this a dumb idea? I'm new to redis so I don't really know what is possible. My thought was that I could store the usage information in redis and then while I'm looping through the subjects, I would combine the usage value stored in redis with the value that had been saved in the database from the cron job. Using Heroku - as I plan - the most frequent cron jobs would run hourly, which I don't think will be acceptable. My quandary is that the current system offers real-time usage information so that will be the expectation moving forward. So I would make a request to a controller that would record the view - via javascript - and then a cron job would move the redis usage data to the database (removing it from redis). I would like to avoid that and am looking at implementing redis to record that information using a technique similar to this post - jQuery Redis hit counter to track view of cached Rails pages In the current system, a database call is made every time the page is loaded updating the view count for that post. One of the requirements is that view information be recorded for a subject.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |