Re: Serving up large images

> > Ah, ER diagrams. Brings back some memories. Happy ones, of course. ;-) > I suppose the file size limitation is to minimize server load. > Exactly. Good luck with your project. > Thanks, Charles. Good luck with your project(s) too. :Darren. -- --

Re: Serving up large images

Ah, ER diagrams. Brings back some memories. I suppose the file size limitation is to minimize server load. Good luck with your project. On 2 March 2010 14:17, Darren Pearce-Lazard wrote: > Click on the link "View Raw File". >> > > Yep. Knew about that but didn't want my users to have the extra

Re: Serving up large images

> > Click on the link "View Raw File". > Yep. Knew about that but didn't want my users to have the extra click. :-) Anyhow, at least for the time being, keeping the file within 1Mb looks to be the way to go. Take care, :Darren. -- --

Re: Serving up large images

> > > Ah ok. :-) You win, Charles. ;-) > > What is the limit? 1Mb? > > Many thanks, Nathan. > > :D > > Approximately, yes. It is subject to change as we tune our > infrastructure over time though. > Ok. Thanks for letting me know. Cheers, :Darren. -- ---

Re: Serving up large images

Click on the link "View Raw File". On 2 March 2010 12:13, Darren Pearce-Lazard wrote: > Hi there, > > For documenting the underlying database of our system, I am creating > database diagrams and storing them in our code repository (in an 'admin' > dir). The file is: > > > http://code.google.com/

Re: Serving up large images

On Tue, Mar 2, 2010 at 1:00 PM, Darren Pearce-Lazard wrote: >> It's the size in bytes. Serving large files ties up resources for much >> longer so we set limits on how large a file we will display in the web >> interface. > > Ah ok. :-) You win, Charles. ;-) > What is the limit? 1Mb? > Many thanks

Re: Serving up large images

> > It's the size in bytes. Serving large files ties up resources for much > longer so we set limits on how large a file we will display in the web > interface. > Ah ok. :-) You win, Charles. ;-) What is the limit? 1Mb? Many thanks, Nathan. :D -- --

Re: Serving up large images

It's the size in bytes. Serving large files ties up resources for much longer so we set limits on how large a file we will display in the web interface. Nathan On Tue, Mar 2, 2010 at 12:53 PM, Darren Pearce-Lazard wrote: >> i'm thinking byte size. > > I assumed it was resolution since a png imag

Re: Serving up large images

> > i'm thinking byte size. I assumed it was resolution since a png image that is quite small (in terms of dimensions) but consists of many colours can be a lot larger than a jpg for the same image. Maybe it's a combination of the two. We'll have to wait and see. :-) Cheers, :Darren. -- -

Re: Serving up large images

i'm thinking byte size. On 2 March 2010 12:13, Darren Pearce-Lazard wrote: > Hi there, > > For documenting the underlying database of our system, I am creating > database diagrams and storing them in our code repository (in an 'admin' > dir). The file is: > > > http://code.google.com/p/migen/s

Serving up large images

Hi there, For documenting the underlying database of our system, I am creating database diagrams and storing them in our code repository (in an 'admin' dir). The file is: http://code.google.com/p/migen/source/browse/trunk/admin/design/database.png