You searched for the word(s): userid:546220

More Search Options

RSS Available

• Re: Best Datamodel for a Social Network?

  The usual approach would be to have the message stored once, with a reference to the user who owns it, the date of publishing, and so on. The (dynamic) list of messages to show on any user's wall comes from a query against the messages published by the user's friends, possibly restricted to a date range, etc. HTH, -LV

  Posted to Architecture (Forum) by LudovicoVan on 11/26/2009

• Re: Genral question on packaging code

  atconway: > When you begin to move into a more formal n-tier (UI->BLL->DAL) design in the future or on another project, I would not reccomend passing the HTTPContext or any object stemming from the System.Web.UI namespace to the BLL or below. As you might know, I would not suggest thinking in terms of BLL's at all. OTOH, I tend to agree with the advise you give here: the general principle simply being that you want your declarations into the servicing layer, not into the client layer

  Posted to Architecture (Forum) by LudovicoVan on 11/1/2009

• Re: Genral question on packaging code

  Look for the HttpContext class . You could pass the Page.Context property in your constructor, but -depending on your specific needs- you could also access the HttpContext.Current property directly, and your support classes could even be static. HTH, -LV

  Posted to Architecture (Forum) by LudovicoVan on 10/25/2009

• Re: Design advice for multiple fields

  My best bet would be a View that joins all the relevant data together and returns the needed rowset. Maybe tedious to write, but I guess that's unavoidable whichever the way you go. If some logic is needed, that could become a stored procedure. In the worst case, I'd still prefer a temporary table with 250 fields rather than string manipulation. OTOH, maybe keep in mind that you can EXECUTE strings of sql statements, which makes room for some code generation. HTH, -LV

  Posted to Architecture (Forum) by LudovicoVan on 10/9/2009

• Re: Family Tree Database Design

  RussUK:> Design 1 seems perfect to me. +1 Apollo.Gonzalez:> I would look at doing something like the following [...] Unless I'm missing something, that just can't work: First, people typically have more than one relation at a time, you'd rather need an n-to-n relationship of the main table to itself. Then, you'd still have to either specify that a specific set of known relatioship kinds is to be considered, otherwise have that evey person relates to every other person where

  Posted to Architecture (Forum) by LudovicoVan on 10/2/2009

• Re: Family Tree Database Design

  [quote user="LudovicoVan"] RussUK:> Design 1 seems perfect to me. +1 [/quote] Sorry, I meant to refer to Vikram's first link: http://25yearsofprogramming.com/msaccess/famhistmdb.htm -LV

  Posted to Architecture (Forum) by LudovicoVan on 10/2/2009

• Re: Business Logic Best Practice

  With some after-thought: > I know that there is not perfect solution or any golden rule when it comes to software. My undergrad in engineering has thought me that; Luckily, that is mistaken: there are some golden rules, even with software. Keep it simple is an example, don't forget your analysis is another one, etc. etc. Rather, that building software must necessarily be a mess, is one of the many false myths about software. HTH, -LV

  Posted to Architecture (Forum) by LudovicoVan on 9/27/2009

• Re: Business Logic Best Practice

  atconway: > > just forget that there is a best approach in absolute, because there is not. > LudovicoVan - thatis is a great statement; you should make that a formal quote! Well, if you like it so much, maybe you should... :) Indeed, jokes apart, that statement is only partly true. A true golden rule is the other one: the keep it simple. -LV

  Posted to Architecture (Forum) by LudovicoVan on 9/24/2009

• Re: Observer pattern-like asp.net projects?

  mendhak: > Duly amended: You can create a SiteMapProvider as LV clearly does not say. Not even, but I'm appreciating the effort. > I like to keep things simple which is why I don't use the P&P blocks anymore. And I like to keep things simple, which is why I do use P&P blocks... How is this possible? > The SiteMapProvider doesn't have a lot to it, it is just an implementation of an interface which makes it easy for the menu to work off, which is sort of what you're

  Posted to Architecture (Forum) by LudovicoVan on 9/24/2009

• Re: Observer pattern-like asp.net projects?

  mendhak> You can create a SiteMapProvider as LV says Well, I didn't actually say that. To be clear: I would not suggest any of the Providers; I just do not like the provider model, it's over-complicated IMO. Instead, I prefer a service-oriented kind of architectures, so here I'd rather suggest a simple static wrapper around the sitemap data and that's all (extremely easy to implement, given that sitemaps support free custom attributes; it also fits very naturally within Asp.Net

  Posted to Architecture (Forum) by LudovicoVan on 9/23/2009