> 134 is good , but what will I do when 134 change for 134567891324? > Got it? No. All images has a uniqe id like every article has. Ofcourse the best is to use guids, but there's no diffenence in serving'em.
One part is to make an interface to all these images, that is and will always be a bandwith and server cpu hog. I would guess that it is not to hard to do the following: 1. make an interface to all articles in somekind of treeview. 2. (featurerequest :( ) when you make a new article, add an extra record to the blobs table that refers to the same blob as the other blobrecord, but refers to a different article. The only problem (afaik) with this approach is the blob itself and repligard. If you do this with a 3 mb blob, and insert it into 5 articles, the xml export will be 3 X 5 mb ;( Tarjei > I started to make such an interface for my admiin site , but I stopped > when I thougt "what about for 3 months?" , "what about getting plenty of images, > and more day by day , only to choose the one I need?" > It is not effective when You have really many many images. > > Piotras > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
