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

More Search Options

RSS Available

• Re: Caching a DS, allow for sorting and paging.

  Optik has it 100% right. Cache the dataset, and use dataviews to perform the sorting... manipulating the elements in a DataTable get exponentially more expensive with .Net 1.1, so make sure you measure your performance gains. If your page only has a few different sort states, then you should try output caching - as ZLA suggested. (In summary, do both, measure... let us know how it turns out! ;-)

  Posted to Web Forms (Forum) by SeanSmith on 7/20/2005

• Re: Singleton Design pattern

  dvdpluijm, Your code above will work fine in your case, so long as your application doesn't create threads within the same HttpContext (I am uncertain whether it is even possible.) Anyway, in the offhand chance you are doing that, you will have to add a two test lock, as so: change this: if (System.Web.HttpContext.Current.Session[SESSIONNAME] == null) { instance = new Singleton(); System.Web.HttpContext.Current.Session[SESSIONNAME] = instance; } to: if (System.Web.HttpContext.Current.Session[SESSIONNAME

  Posted to Architecture (Forum) by SeanSmith on 7/13/2005

• Re: Modeling a scalable Roles architecture

  I would avoid modelling every single capability due to the reasons that mbinnix indicated. You don't want to have to audit 2000 capability to role mappings. Our project has a data driven menu, and each item on the menu is treated as a "capability". Each menu item can be associated to 1:m roles, and each user can be mapped to 1:m roles. In addition, some roles may only have read only access to a menu item. Our menu exposes the current menu item to the rest of the application, and the data access layer

  Posted to Architecture (Forum) by SeanSmith on 7/12/2005

• Re: Migrating system to 3-tier architecture

  I would suggest you begin by creating a test harness, or unit test for the existing code. The larger the system, the more important it is to have some sort of functionality verification test that works for the existing system, in order to validate the system after you refactor it. Whether or not you refactor, or redesign in place is a matter of taste, so long as you have a formal and thorough test to verify the code is functioning properly. Look into "Working Effectively with Legacy Code" by Michael

  Posted to Architecture (Forum) by SeanSmith on 7/9/2005

• Re: Modeling a scalable Roles architecture

  I'm not sure if this is what your looking for, but I like to address these issues by having "Process" classes that reside in an class library just for processes.

  Posted to Architecture (Forum) by SeanSmith on 7/6/2005

• Re: Binding ArrayList to a DataGrid

  Andy, The grid is showing the whole object because you have AutoGenerateColumns="True". Try the following: <asp:DataGrid id=grid AutoGenerateColumns="False" Runat="server"> <columns> <asp:BoundColumn DataField="Title"></asp:BoundColumn> </columns> </asp:DataGrid>

  Posted to Data Presentation Controls (Forum) by SeanSmith on 7/4/2005

• Re: Not simply ORM eliminates one tier

  Oh, hehe, well, I reread the post after your translation... and it actually made alot more sense... I guess I was expecting a question in there somewhere and was thrown off...

  Posted to Architecture (Forum) by SeanSmith on 7/3/2005

• Re: Factories - Entities

  RogerK1975, I generally mark constructors internal on classes I intend to have instantiated by a class factory or a builder. For classes that I intend to be created through a factory method, I mark them private. It is not something you have to do however, it just enforces use of the factory. You may not need to enforce that usage now, but in the future you may. Common reasons to enforce factory usage is to make sure an object repository, cache, or logging event is aware of the object. On a less productive

  Posted to Architecture (Forum) by SeanSmith on 7/3/2005

• Re: anybody have a experince in OODBMS?

  erdsah88, It sounds like your issues may not be database issues. If your custom data mapper evaluates the mapping at runtime, you should compute the cost of that runtime evaluation, and look into ways to make that faster, or to move that evaluation to compile time. Maybe look for a good profiler... I'd be interested to know how an OODB affected your problems, should you take that route.

  Posted to Architecture (Forum) by SeanSmith on 7/3/2005

• Re: Object Model vs Data Model

  Voodooo, The posters above indicating that you should work on both simultaneously are absolutely correct.. However, it is also largely dependant on your personal tastes, your background, and your application. If your a top down thinker, or if you have more OO experience than DB experience you will be more comfortable in the object layer. The opposite is true if your a bottom up, or relational data person... The important thing is to realize it doesn't matter which you do first, as long as you spend

  Posted to Architecture (Forum) by SeanSmith on 7/3/2005