Clemens Vasters: Enterprise Development & Alien Abductions
Thoughts about Microsoft .NET, Enterprise Services, XML and other dull and boring things.
Updated: 7/30/2002; 8:47:49 AM.

 














Subscribe to "Clemens Vasters: Enterprise Development & Alien Abductions" in Radio UserLand.

Click to see the XML version of this web page.

Click here to send an email to the editor of this weblog.

 
 

Saturday, July 27, 2002

ASP.NET state management with style (& attributes). Now *this* is the way that state should be managed in ASP.NET! [sellsbrothers.com: Windows Developer News]

I'll post a little update tomorrow (I hope), which will polish this up to perfection allowing you to share the persistent state and session state values across pages in this fashion. The required changes fit into 5 lines of code or so, but I am doing something else right now.


6:36:47 PM      comment []

Ukrainian Plane Kills 70 Spectators. This is such a tragedy, I am shocked.
6:18:54 PM      comment []

Sam Ruby seems worried that I am mad at him, saying "The (hopefully friendly?) banter continues.". All absolutely friendly disagreement for sure.  ;)

And then he says in reaction to my reaction on ALTER TABLE:  "Hmmm.  Somebody told me that the "X" in XML stood for eXtensible too.  All I ask is that you just keep an open mind, and let me make my case.".

Will do. Just keep in mind that the "L" in XML stands for "Language" and that it is an "extensible language", not an "extensible document instance format". You define languages and use them. If you unilaterally decide to arbitrarily change the language rules or mix them, that's not good. For me "Harumpf" wasn't in the vocabulary, so I had to look it up elsewhere and since the definition wasn't clear, I had to make a guess on what you meant. The Hauptproblem with dieser Sache is dat ik niet einfach the language change kann as I wünsche, weil uw niets mehr understand würdest. (If you know what I mean).

The true gem in what you've written yesterday:  "As to your example, there is no question that two "customer" entites that are semantically different should be modelled separately". Modeled differently, identified differently, even if both classes look exactly alike. You can't steal someone else's class, if that could get you in trouble later. Two namespaces. Thanks, Sam, that's exactly what I say.


9:49:00 AM      comment []

As to your example, there is no question that two "customer" entites that are semantically different should be modelled separately.  The question to ponder is whether or not "ALTER TABLE table_name ADD column_name datatype" should be allowed and what the implications of this are. [Sam Ruby]

I don't think that database dumps are used much to move data between different organizations, nor are SQL/CLI connections across organization boundaries commonplace -- someone told me that there was this XML thing that does this stuff better. You can play with your internal schemas, may it be for databases, XML or stuff like Active Directory or WBEM, as much as you wish as long as you don't tell anybody outside your own control boundaries. Once you put stuff onto the edge of your control boundary, Schemas must become reliably well-defined and stable. The control boundary, of course, depends on how many people you can boss around in your shop.


1:57:06 AM      comment []


© Copyright 2002 Clemens Vasters.



Click here to visit the Radio UserLand website.

 


Send email to Clemens
July 2002
Sun Mon Tue Wed Thu Fri Sat
  1 2 3 4 5 6
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30 31      
May   Aug

newtelligence
MSDN Regional Director