1.its a web app containing inside multiple apps
2.each is called a component.
3.each component can be accessed independently by different users logging from different locations by an account
4.primary handle to a login session is based on user name and password.
5.a handle will be obtained for the session.
6.this handle typically identifies an entry in static login table in the database.
7.Now there can be different operations like create smthg,delete,modify etc based on the handle
8.a user ui session calls on the component with the handle,the event handler identifies the current
context with the handle.
9.the context will be a row with n coloumns,each coloumn containing separate sql formula (pointers)
10.the entry point of the event will update this context and refresh,after that every successive operation with the context should refresh before using it.
11.this makes the context in nnn(context,request)
12.the event handler can be a separate java lib,scripts etc(binary mapping,inplace loading)
13.prefer scripts over lib
14.how to load two batch files in an application and call a function in one batch file from other in the context of application.
15.event handler ultimately gathers some other contexts into its workspace , manipulates and writes something back to contexts or updates some data base tables, or passes on to next call.
event1:
get context from handle1, and data
do something
get handle for event2 in another module
call event 2 pass handle, and data
get context2
16.some context row can reserve a column for unknown handle
17.when this context is passed to another module it can access the unknown modules handle which is a depenent db
No comments:
Post a Comment