I am developing a web application that is really nothing more than a catalog for my company. (The company distributes medical clothing)...
I have a class PStyles
and a class PStyleCollection (which is exactly what it sounds like)... Then in the datalayer, there is a function that returns PStyleCollection to be used as a repeater datasource on the front end...
Here is my question. And, I don't expect there is a real answer, I just want some opinions.
At the moment, when each PStyle is displayed, I link to an image on the server... So, what I am considering is actually including an image as part of the object...
Private _styleImage As Image
...
Public ReadOnlyProperty StyleImage As Image
Get
Return _styleImage
End Get
End Property
One issue I can think of is that at any given time, there are about 100 or so styles in the collection. And, unless the user is using filter, the entire collection gets returned. That is a lot of images in memory...
Thoughts?
I have a class PStyles
and a class PStyleCollection (which is exactly what it sounds like)... Then in the datalayer, there is a function that returns PStyleCollection to be used as a repeater datasource on the front end...
Here is my question. And, I don't expect there is a real answer, I just want some opinions.
At the moment, when each PStyle is displayed, I link to an image on the server... So, what I am considering is actually including an image as part of the object...
Private _styleImage As Image
...
Public ReadOnlyProperty StyleImage As Image
Get
Return _styleImage
End Get
End Property
One issue I can think of is that at any given time, there are about 100 or so styles in the collection. And, unless the user is using filter, the entire collection gets returned. That is a lot of images in memory...
Thoughts?