How about the size of message being written to an MSMQ? I've seen a couple of different scenarios here.
1. The developer isn't aware there is a limit, so does nothing to ensure the message is below it. 2. The developer is aware, but has misunderstood the limit expressed in the docs as the number of characters, not the number of bytes. (Or hasn't misunderstood, but is unaware .Net strings are Unicode by default.) Keep Smilin' Ed Stegman -----Original Message----- From: dotnet discussion [mailto:[EMAIL PROTECTED]]On Behalf Of John Lam Sent: Wednesday, May 29, 2002 7:59 PM To: [EMAIL PROTECTED] Subject: Aspects as diagnostic probes, WAS: RE: Re: [DOTNET] AOP to police thread affinity? One thing that I've been spending a lot of time thinking about recently is using aspects as diagnostic probes. That was why I was sending out emails asking questions like "what are the top 10 mistakes that you see folks making when writing .NET code". It is certainly possible to write some an aspect that will enforce thread affinity at runtime. In fact, I've added that to my list of interesting diagnostic probes to write. I've written other experimental diagnostic probes that do interesting things like: 1) Enforce limits on the size of ViewState in an ASP.NET page 2) Enforce limits on the size of Session state in an ASP.NET application 3) Enforce limits on how long a database connection can be held open for I can see lots of value in using these things, particularly if the folks who wrote that technology, or folks who are intimately familiar with that technology can capture their knowledge inside of a diagnostic probe / aspect. Do folks have other interesting ideas for aspects as diagnostic probes? -John http://www.iunknown.com You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
