architecture

问题 I have worked with MVC on the back-end (Rails), and am currently working with MVC(MV*) on the front-end (Angular). I have seen Angular as considered an MV* pattern, but why is it considered that exactly? Using Angular, I understand the separation of concerns, with Views (templates), Controllers, and use Services to serve up data. In this case, the model (data store) via ng-model makes sense for front-end temporary storage, but the actual persistence (when a POST or PUT is made to an API)

问题 I have a requirement where in I have a set of jobs to be executed from the screen (each job could take hours to execute) and I need to put some rules in place to execute those jobs. it can be represented using a graph. each job is given a sequence number and jobs should be executed in sequence however there are set of jobs that can be run in any order and each of them may have a path of their own. for example once A and B are finished, D, E, F can be run in any order, but there can be a rule

问题 I'm new to scenekit, so when I started my first project I noticed it's slightly different from spritekit. Although not ideal, I used to use 1 gameviewcontroller and 1 gamescene in spritekit to code my entire game. (YES, this includes a menu, game/levels, settings, etc...) I'm now wondering since I'm using SCNScenes (which are just loaded from the viewcontroller), I do not want my 1 view controller to be swamped with code. What is the best way to layout a game? Should i have 1 viewcontroller

问题 I don't think the question is clear here. Simply I have 19 types of items in my system. and I have 19 pages each one allow me to add a new item of specific type. The "Add New Item" page and the "Edit an existing Item" page, are very similar from each other .. all what I need is to hide/show a couple of controls. so I thought I'd use QueryString to define how we'll be using the page, if new then everything will remain the same and if it's used for "editing" then I'll change the Text properties

问题 I have a layered architecture as follows; Presentation Service Business Data If I implement MVP for the presentation my understanding is that the Service Layer represents the 'M' i.e. model, is my understanding correct? If so from my interpretation of MVP the model can raise events which my presenters would subscribe to. Does this mean that my service layer would raise events? UPDATED This question has been viewed a number of times but has not attracted any comments or answers, if there is

问题 I have an idea to compile C++ to a binary, store the binary on the heap and execute it. I was considering one implementation of compiling to specific architectures like Google Native Client does, then knowing what architecture I have compiled to, use the same or a different compiler -- at run-time -- within my program to compile a "snippet" or "script" and output the machine code to memory allocated on the heap. Then point a function pointer to the right place and run it. My question is,

问题 I am building a multi-site platform, similar to StackExchange in the way that it has several communities using the same platform and sharing data. Users can "tag" their content the same way you can tag a stack exchange question. What is the best architecture to create a tag concept? Some small notes I thought about was the concept of aliases (synonyms). Also I thought on one hand I want tags to be shared across sites (so one can see content from another site on the same topic), but on the

问题 We have an SSO system for authenticating users. We have a debate between these 2 options: Should we centralize the authorization of each application to one database (or any other single solution) and retrieve the information within the SSO request Each web application client should manage it's own authorization logic in it's a local database / scheme. 回答1: You should strive to decouple your business logic from non functional requirements such as authentication, logging, and of course

问题 In the everyday front-end development I often use DOM as a global event bus that is accessible to every part of my client-side application. But there is one "feature" in it, that can be considered harmful, in my opinion: any listener can prevent propagation of an event emitted via this "bus". So, I'm wondering, when this feature can be helpful. Is it wise to allow one listener to "disable" all the other? What if that listener does not have all information needed to make right decision about

问题 I have a problem to decide which layer in my system should create DataContext. I have read a book, saying that if do not pass the same DataContext object for all the database updates, it will sometimes get an exception thrown from the DataContext. That's why i initially create new instance of DataContext in business layer, and pass it into data access layer. So that the same datacontext is used for all the updates. But this lead to one design problem, if i wanna change my DAL to Non-LinqToSQL