Skip to main content

crunching pop corn...

I am in the midst of the implementation of the solution mentioned at the end of sent2null space: objects , abstractions, symmetry and pop corn??? I ran up against an issue that happens occasionally when a modification is made to a class model. You'll recall , I realized that the uniqueness of guest invitations could be used to define the conference type and allow an existing conference to be used as proxy...while investigating deeper, I realized there is no need even for the proxy if I change the structural rules behind the table that tracks conversation participation. In my framework this table is called appropriately the participant_queue it simply lists the attributes of Users engaged in conversations. The database schema for the table enforces referential integrity for a column called conversation_id , in the original implementation of the collaboration API the idea of guest Private messages was not supported, only guest conference users were supported and since a guest to a conference is always joined to an existing conference on the system , referential integrity for conference id's made sense ...but to support guest PM's I could either add a new type and then create new managed conferences for every guest PM request as mentioned in the previous post but this is computationally as well as resource inefficient, especially as large numbers of guest PM requests come in. To allow for efficient guest PM's an unmanaged interaction would be ideal, the solution as mentioned previously was to use the uniqueness of guest pm requests...I realize now that the minimal effort and maximal pay off comes from relaxing the referential integrity constraint of the table column conversation_id and using the existing methods for adding , retrieving and updating conversation rows based on the participant attributes. This single action allows me to readily support the specific symmetry of guest PM's without requiring managed conversations (with valid conversation id's) to be used as proxy, by using zero value conversation id values to correspond to guest PM participant rows in the conversation_id column I can track guest PM's independent of valid managed conversation objects (those with positive integer id values) the drawback to this is only that I have to recompile my existing test instance of the application and reinstall it (strictly speaking I don't since I can modify the constraint via the db admin tool) anyway I decided to just make the change and forgo all the other hassles of needing to update the add, update and retrieval methods of the conversation objects. So this is a perfect example of observing a particular symmetry in action, in this case it is the symmetry of the database schema when the table constraint is in place, I couldn't use negative or zero values...but by relaxing that constraint use of zero or negative values allows me to employ them for the use of the guest PM's which now can be instanced entirely in memory without management resource allocation on the db which is a key drain in performance especially under scaled conditions.

I'll be explaining more about the actual implementation as I role through it in the next few days.

Comments

Popular posts from this blog

Deconstructing Landmark Forum

Deconstructing Landmark Forum:




Prologue:

Recently I was introduced to the Landmark Education organization by a girlfriend, she was effusive about the many lessons she learned and the "breakthroughs" she had while taking their "forum" and other self help and improvement seminar programs. I was immediately credulous, as a student of science I often find myself playing the advocate of reason when discussion emerges over any particular topic. Often the subjects that provide the most fuel for application of this reason based approach to information analysis are seemingly difficult to quantify without descending into machine gun fire ejaculation of "ideas" with little but anecdotal support behind them. The books of experience that people in various areas serve as the guide for their views a priori of new evidence, this bias against the future by correlation with the past often serves to hold people back from changing their views to suit
new observations...the…

Engineers versus Programmers

I have found as more non formally trained people enter the coding space, the quality of code that results varies in an interesting way.

The formalities of learning to code in a structured course at University involve often strong focus on "correctness" and efficiency in the form of big O representations for the algorithms created.

Much less focus tends to be placed on what I'll call practical programming, which is the type of code that engineers (note I didn't use "programmers" on purpose) must learn to write.

Programmers are what Universities create, students that can take a defined development environment and within in write an algorithm for computing some sequence or traversing a tree or encoding and decoding a string. Efficiency and invariant rules are guiding development missions. Execution time for creating the solution is often a week or more depending on the professor and their style of teaching code and giving out problems. This type of coding is devo…

AgilEntity Architecture: Action Oriented Workflow

Permissions, fine grained versus management headache
The usual method for determining which users can perform a given function on a given object in a managed system, employs providing those Users with specific access rights via the use of permissions. Often these permissions are also able to be granted to collections called Groups, to which Users are added. The combination of Permissions and Groups provides the ability to provide as atomic a dissemination of rights across the User space as possible. However, this granularity comes at the price of reduced efficiency for managing the created permissions and more importantly the Groups that collect Users designated to perform sets of actions. Essentially the Groups serve as access control lists in many systems, which for the variable and often changing environment of business applications means a need to constantly update the ACL’s (groups) in order to add or remove individuals based on their ability to perform certain actions. Also, the…