Timeline for Reporting Solution in PHP / CodeIgniter - Server side logic vs client side
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 22, 2014 at 19:28 | comment | added | bign8 | Yes Robert, but you are still subject to network (which for 200,000 records could be a bit) lag by off-loading all your processing to a server. Both cases work, it is just a developer's preference which one he/she chooses. | |
| Jan 22, 2014 at 19:23 | comment | added | Hackerman | That's what i'm talking about...and if you use the right stored procedures to produce a decent pagination, your app should works like a charm | |
| Jan 22, 2014 at 19:20 | comment | added | bign8 | That is getting toward the cap for client processing. What I would recommend is mocking up a client side example and try some performance testing to determine if you should perform the logic on the server or not. Personally, I prefer to use client side logic and just have my servers respond with data-chunks. But in the end, the decision is yours. | |
| Jan 22, 2014 at 19:19 | review | First posts | |||
| Jan 22, 2014 at 22:52 | |||||
| Jan 22, 2014 at 19:14 | comment | added | dot | yeah... that's what i was thinking too. I'm going to be using jquery. We're talking about 200,000 records or so as the upper limit and 1000 as lower limit | |
| Jan 22, 2014 at 19:03 | history | answered | bign8 | CC BY-SA 3.0 |