Quantcast
Channel: Posts/rss
Browsing latest articles
Browse All 12 View Live

Comment from Hakan Bilgin

Hi Jonathan, Even though it is not new, I would like to emphasize that these rules, slightly modified, can be applied to client/server instead of web-server/database. The solution is of course XML+XSL...

View Article


Comment from Pat Allan

I'm not sure about the older ADO connections, but ADO.NET definitely handles connection pooling for you automatically. My understanding is that you do close the connections yourself, as soon as you've...

View Article


Comment from Jonathan Snook

Reg: even with connection pooling, you still have the issue of available connections in the pool. The sooner you can release a connection back into the pool, the better. Also, the data provider often...

View Article

Comment from Thomas Messier

Thanks for the link to Jay Pipes, it was a good read. While I feel that caching to disk as shown in the article is probably not the most efficient way to go, the example illustrates nicely at a...

View Article

Comment from James Bennett

One of my favorite tricks for this is in ORMs that let you "select related" -- they'll work out what objects you explicitly asked for, and if you tell them do "select related" they'll also figure out...

View Article


Comment from Reg Braithwaite

This is a good tip with low-volume sites. However, with high-volume sites the overhead of opening and closing connections becomes significant. Thus, many frameworks (I won't say MVC frameworks, this is...

View Article
Browsing latest articles
Browse All 12 View Live