Good point. Also, it might be worth considering delegating the heavy-duty work to a server-side process, either via the database (procedures, etc.), or servlet, etc.
Type: Posts; User: dlorde
Re: What is the best way of designing this object?
Good point. Also, it might be worth considering delegating the heavy-duty work to a server-side process, either via the database (procedures, etc.), or servlet, etc.
Re: What is the best way of designing this object?
It sounds like the problem is logistical and database related - there are plenty of no-cost and open-source Java database engines out there (e.g. Apache Derby, JODB, etc.), why not use one of those...
Re: What is the best way of designing this object?
Presumably you've tried increasing the Java heap size?
Do you really need all those routes in memory at once, or could you read/write/replace them on demand from a database?
What are the...