Message encoding

DS while taking a walk out was called in for a sudden meeting. Keeping the timing in mind it was something he couldn't refuse to attend. In he went and was there for a surprise.Everything happed was somehow linked to something which happened before and the encoded message was so explicitly open that it probably had no need for encryption. But pity that someone still believed in it and DS had no other option than to buy it.

 Just a day before, involved in a discussion DS opined about something which a senior arse found offending !! not because that it was offending but because whole exercise from his side was to cut DS out and being in the system DS well aware of  knives around had to protect the interests which technically suited more in DS favor. But it actually resulted in  tunring the knife back in the stabber's direction which arse found offending as pricking of it hurt. Prick was certainly offended ;) Worst part, a man with no control cries his heart out and shouts at everyone and blames for his pain. This Prick was no different. But then something unexpected happened. There was a person sitting neutral to observe DS, who happened to observe this prick this time.

DS realized that person immediately received  a call after the discussions for live updates which appeared more like a curious plan. It was really amazing to see the politics at its best in world of folks who can play it as dirty as the shit ball can contribute. Worst for Prick that it went up with all details and realizing the sensitivity of   issues Prick had to safeguard himself. He went out for the dressing and to heal the wound apologized to world for crying his heart out. But this probably which DS doesn't know had some link with live update client linking linking it to master sniffer. Sensing the corruption Sniffer might have looked more in details and found the pattern wrong. Prick might have been called for the clarification and possible cause. Which Prick attributed to DS's AD-HOC way of bringing forward any technologies without keeping the system aware of protocols and in absence of necessary infra the packets resulted in corruption. The whole system crash was attributed to DS. Sniffer than sniffing the problem attempted to talk to DS for defining the protocol.

The advantage, Sniffer had was the improved informations for it to interrpret that and moreover it could cause no derailment of project.

Interesting part now about this is the message encoding which Sniffer coded and sent to DS for interpretation :

Sniffer suggested that DS should only look at the header part of the protocol and not worry about the other parameters bounding. Moreover in each header only the specific parameters should be added and not the ad hoc informations from anywhere. Advantage of that model would be that it won't derail the project.

DS in short concluded the encrypted message so explicitly suggested that some senior crocked arse has gone ahead and complained that DS is bringing out any ad hoc concept and not working on the stuffs he is supposed to do. This is de railing the project and causing damage.