Tag Info

New answers tagged

1

This http://www.unigui.com/ seems relevant. This seems also close https://forums.embarcadero.com/thread.jspa?messageID=510208&tstart=0. I guess your old "business layer" code is written with Borland tools, either C++ or Delphi? Some decade ago I was porting lots of legacy code from 16bit DOS (Turbo Pascal) to 16bit DPMI (Borland Pascal) and to 32bit ...


0

@JBRWilkinson is right, basically. Having a web client front end and a web server backend is a highly asynchronously thing by definition. Especially when callbacks come into play to dynamically load data or verify things, etc. But you don't have to rewrite the whole app. You don't need to rewrite the workflow either. You "only" have to work on those parts ...


0

> Reworking/rethinking these workflows is not an option I am afraid you have to add additional states in your workflow, every time the old workflow asks for a user-decision without changing the base workflow. example in old system: customer adds products to basket ... checkout: customer decides to buy the content of the basket system does the ...


1

Read up on asynchronous programming It sounds like your original desktop app was tightly coupled with the GUI with functions not continuing until user chooses decisions from popups. The web, and many GUI frameworks, just don't work like this - all operations that may require user input have to provide a delegate/callback so that processing can continue. ...


0

Disclaimer: I am not a super experienced web developer. I believe that javascript/the client side of web apps are not usually written this way, as no matter what, in most browsers all js code is run in one thread. However, you can simulate this behavior, with something like this (I have never used it, it's just what I found), to pause a thread (pseudocode): ...


0

I have done a lot of searching but I am still not able to figure out where exactly should I place this Python file containing all the logic. There are a number of options, depending on what your requirements are: Add the logic to e.g. the Image model. This is a useful option if you need to store per-image meta data in the database, and each model ...


0

Daniel Greenfeld, co-author of "Two Scoops of Django, recommends the business logic should be in the models "when possible, or in the forms if you must." As for Bart's possible duplicate, django may be similar to MVC but it is not MVC. As explained here in the official django documentation faq. @adrita, I think you need may need to go review the official ...


6

Your primary difficulties I feel are that you have a mismatch between a very linear and custom workflow in an older application that do not coincide with the user interaction workflows that are common on the web. Web applications that interact with a server application that contain the business logic communicate in a Request/Response messaging style. The ...


0

My preferred responsibility by object: Controller handles the building of the viewmodel/viewbag. Logic unrelated to the rendering of the page gets shipped off to the BL. Thus personally I would compose the viewmodel within the controller, and not create a separate layer. The layer that you would create to compose the viewmodel, what would you call it? The ...


2

For me there is no question to be answered here, you should always strive to separate out your components as much as possible. At a bare minimum, for every new project I create I do the exact following steps: 1) Create a blank visual studio solution 2) Add an MVC project to it 3) Add a class library to it called the Business layer 4) Add a class library to ...



Top 50 recent answers are included