business-logic

问题 I often see the phrases 'business logic' and 'application logic' in terms of web development (I assume it also applies to programming in general rather than just web development). This is quite new to me so I don't really know what it means, could anyone please explain me what is exactly meant by this? Is it just a 'buzz word' used by programmers? Or? 回答1: Business logic is basically rules of the system according to functional specifications. For example Object A of type B must have

问题 i'm new to appcelerators titanium and javascript and i'm interested in coding an iphone app. i recognized that there is a need of "many" code for creating the UI. that's no problem so far, but i tend to separate that code from my application logic wisely. what are the best practices? [update] tweetanium is a great example how to structure a titanium mobile application 回答1: ok, i just found a cool practice. i include the con_file.js with the application logic the view_file.js with Titanium

问题 In separate data access & business logic layer, can I use Entity framework classes in business layer? EDIT: I don't think I will need to swap out the data access layer from my business logic in the future (i.e. will be SQL Server), however I will for the UI layer. Therefore the question is more meant to be are there any major issues with using EF classes for me in the business layer? Seems like there would be less plumbing code. 回答1: Typically, the "best practice" approach would be something

问题 Derik Whitaker posted an article a couple of days ago that hit a point that I've been curious about for some time: should business logic exist in controllers? So far all the ASP.NET MVC demos I've seen put repository access and business logic in the controller. Some even throw validation in there as well. This results in fairly large, bloated controllers. Is this really the way to use the MVC framework? It seems that this is just going to end up with a lot of duplicated code and logic spread

问题 suppose you have an MVC application with the Model represented by an Entity Framework (EF) that "gets" data from a database and the action methods of the Controller that implements all the business logic. The Controller gets data from the database through the EF. Imagine that now you create a Repository class that is placed between Controller and Model. This way you have: 1) Controller : implements most of the business logic; 2) A Repository class , responsible to implement simple business

问题 Closed . This question needs to be more focused. It is not currently accepting answers. Want to improve this question? Update the question so it focuses on one problem only by editing this post. Closed 6 years ago . Specifically, the EIS (database) Tier versus using the Web tier with POJO's and a light framework or the standard business logic tier using EJB's. Also, there may be other options besides these that I'm not aware of. Basically, it's design considerations for business logic with

问题 I want to ensure that the state of an object is always valid. Let us assume a class with a constructor and a setter: class MyClass { double x; // Must be in [0;500]. public: MyClass(double _x) : x(_x) { if (x < 0.0) throw /*...*/; if (x > 500.0) throw /*...*/; } void SetX(double _x) { x = _x; if (x < 0.0) throw /*...*/; if (x > 500.0) throw /*...*/; } }; This has several drawbacks: The validation code is redundant. (in constructor & setter) The rules exist for the class in general, and not

问题 It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center. Closed 8 years ago . I'm developing a web application that involves businesses signing up. What is the best way to verify a businesses identity? How do I know the person signing up for "Pizza Hut" really works for Pizza Hut? Are

问题 C#, LINQ to SQL Some advice me to open new topic insteed that topic becouse there is no solution for my problem. Now I will need your help to re-design my layers. Linq To Sql - Making a dynamic search for the Application layer without exposing DAL layer as DLL My project consist of 3 layers: DAL, BL, Application. The Linq2Sql is exsist in the DAL layer and he auto-generate a class to each table in the data base, and a ContextObject to manage the data base. I cant change anything in this

问题 I want to know where in my code I should place my business logic. Should it be in my model or should it be in the controller? I have always thought it should be in the controller but I have been told by a friend that I should put it in the model. Any help would be appreciated. Thanks, Sachin 来源： https://stackoverflow.com/questions/9810028/placement-of-business-logic-in-mvc