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

the attributes of web 3.0...

As the US economy continues to suffer the doldrums of stagnant investment in many industries, belt tightening budgets in many of the largest cities and continuous rounds of lay offs at some of the oldest of corporations, it is little comfort to those suffering through economic problems that what is happening now, has happened before. True, the severity of the downturn might have been different but the common factors of people and businesses being forced to do more with less is the theme of the times. Like environmental shocks to an ecosystem, stresses to the economic system lead to people hunkering down to last the storm, but it is instructive to realize that during the storm, all that idle time in the shelter affords people the ability to solve previous or existing problems. Likewise, economic downturns enable enterprising individuals and corporations the ability to make bold decisions with regard to marketing , sales or product focus that can lead to incredible gains as the economic

How many cofactors for inducing expression of every cell type?

Another revolution in iPSC technology announced: "Also known as iPS cells, these cells can become virtually any cell type in the human body -- just like embryonic stem cells. Then last year, Gladstone Senior Investigator Sheng Ding, PhD, announced that he had used a combination of small molecules and genetic factors to transform skin cells directly into neural stem cells. Today, Dr. Huang takes a new tack by using one genetic factor -- Sox2 -- to directly reprogram one cell type into another without reverting to the pluripotent state." -- So the method invented by Yamanaka is now refined to rely only 1 cofactor and b) directly generate the target cell type from the source cell type (skin to neuron) without the stem like intermediate stage.  It also mentions that oncogenic triggering was eliminated in their testing. Now comparative methods can be used to discover other types...the question is..is Sox2 critical for all types? It may be that skin to neuron relies on Sox2

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 cert