most of the time it is safer to partition the data into more manageable chunks.
Agreed. But there is no good way to solve my problem.
I'd be happy to give my example; if you can point out a simple way to reorganize my 70 page of model, I'd be very happy. :-)
(No, I'm not a complete idiot that has done something simple in a complex manner; it was a very hard problem.)
It's a pretty dangerous route to go down, making your app depend on getting the same process every time, since it hurts your scalability.
Very good point. If this could get heavy use, I'd write it so the different backend servers had different DNS addresses for active sessions, then it should scale. Of course, another server could take over the job (heartbeat) -- but would have to reinit the data.
But when that design start to trash (not enough memory for all models of all users), I'd start to cry. :-)
| [reply] |
If you start a new thread for it, I'd certainly read it and offer ideas. Starting it buried down here is probably not a good idea.
| [reply] |
