FX Settlements

The CLS website has a great picture on how settlements work for FX trades. Here it is:





CLS is a bank set up by a consortium of different financial firms. It what my client uses for settling their FX trades.


©2006 Marc Adler - All Rights Reserved

Services for the Wall Street Stack

I have blogged before about the need for a standardized Wall Street Stack. At my current client, there are several different frameworks that have been built over the years, but no framework has gained enterprise-wide acceptance.

These are the services that are generally needed for a complete application framework. If you can think of any other, let me know.


Authentication - logging in to various databases, web servers, internal systems, etc. Best implemented through an enterprise-wide authentication service (using the user's Kerberos token, etc)

Authorization (Entitlements) - what actions can a user perform within an application and what data is a user entitled to see. Best accomplished through an enterprise-wide system.

Logging - log interesting things that happen in an application. Log4Net is a good framework.

User Preferences - load and save the state of the UI

User Data - each application may want to persist the last state of the application when the user logged off

Configuration - Each application should be configurable through a series of XMl files.

General Services Manager - drives the entire service locator framework

Applet Management - load applets from .NET assemblies

Internal Event Broker - lightweight communication between applets

Data and Persistence layer - ways to load, query, update and cache data. Should be configurable so that we can go through different transport layers

Service Agents - processed async notifications that come to us through subscriptions.

Shell - handles initialization of the application, calls all of the various services, provides presentation services for the applets

UI - menu manager, status bar manager, navbar manager, toolbar manager

Security/Cryptography - does the data need to be encrypted and decrypted? (passwords, sensitive data)

Exception Handling - provides a unified way of handling errors that occur in shell and the various applets

Threading - model for async processing


©2006 Marc Adler - All Rights Reserved

Universal DBs

Lately, I have been talking with IT directors at various financial firms. There seems to be one consistent message --- The holy grail that all of the financial firms are seeking is the universal database, where all trades across all asset classes can be held.

This is especially problematic at financial firms who keep buying other firms (Wachovia, Bank of America).

OLAP is a hot skill right now, and companies what to perform sophisticated queries over huge amounts of data. Finetix currently is working in the OLAP space int he commodities area of a major financial firm. This firm has asked Finetix to invent a cloning machine so we duplicate our 3 OLAP stars and sprinkle them throughout the firm. Maybe I should start attending Andrew Brust's presentations at the various .NET user groups.

©2006 Marc Adler - All Rights Reserved

How Do They Find Me?

I have been getting a bunch of calls from recruiters at my desk at my current client. I think that they know the telephone prefixes of the IT departments at the various Wall Street companies. The recruiters call every single number with that prefix in the middle of the night, and wait for the voice mail to kick in. So, they can get a name of a person at a desk at a Wall Street company.

The calls then come....

Recruiter : Hi Marc. I know someone who worked with you at your last company and they thought you were great.

Me (seeing the bullshit form a mile away) : That's fantastic! What company was that?

Recruiter : (sound of frantic typing in the background). Did you say that this was Marc Adler? Hmmm... it was ... XYZ.

Me : Who was the person that referred you?

Recruiter : Let me tell you about this position.

Me : (hangs up)

A recruiter's opening line says everything about his veracity and ethics. If a recruiter comes across like a telemarketer, I will not deal with him. A better line might be :

Recruiter : Hi Marc. I have been retained by Bank of America to hire a team that needs to build a credit derivatives system. Their platform will be a .NET front end, Java backend, wired together by Tibco EMS. Since you are working now for XYZ, and since I know that their credit derivatives systems use that precise technology, I was wondering if you or any of your teammates would be interesting in implementing a system like this over at BofA. Of course, the compensation would be above and beyond your current salary, which given your level, I could probably take a guess at.

Why is this good? I find out the name of the company who is hiring, and I already know that it's not with the company that I am currently with. (The worst thing is to find out that the job is for your position at your current company!). I see that the recruiter has taken the time to find out that I am with the credit derivs area, and has taken the time to know that my current client uses a particular technology. I see that the recruiter is aware of current salaries and could divine what it would take for an established player to move to another company.

I don't want to have to play games with a recruiter to find out about a position. Be straight, be honest. If I am truly interested in something, then I will not do an end-run around you.

Also, do you guys realize that, if you call me in the middle of the day, then the 5 people who sit around me usually hang on every word that I say on the phone?


©2006 Marc Adler - All Rights Reserved

Interesting Call From Microsoft Recruiting

It used to be where millions of applicants would send their resumes to Microsoft in hopes of a job. Howver, this is not your father's Microsoft anymore. The stock has been in the shitter for the past few years (I sold mine for a split-adjusted price of $30 in 2001, and the stock has never gotten higher), and the options program has been dessimated.

Somehow, a Microsoft recruiter got a hold of my name from some past colleague. There is a developer evangalist position open in the New York/New Jersey area. I happen to know the person who just left that position; he had been a familiar face at the various New Jersey .NET User Group meetings. This is not a bad position .... you get to go to companies and user groups around the NYC/NJ area and talk about the latest MS technologies from a developer perspective.

So, this recruiter kept calling and calling. I was not interested in the position at all, but I wanted to get another data point and hear what MS was offering senior-level architects and devs now. She would call me in the middle of the day, at my desk at my client, and I would patiently explain to her that I could not talk about a new job with 5 people sitting around me. She would make plans to call me in the evening, but then had to go pick up her kids somewhere, watch her neighbor's kids, etc. Always some excuse.

We finally managed to connect this week. She started to explain the job to me, but I told her that I was already very familiar with the responsibilities of the position. I told her to get down to brass tacks. What were they paying? I told her what my current base salary was so that we could start negotiating. My hopes would be that she could come close to the base,

She looked in her little black book, muttered to herself "hmmm... since this IS in the New York area, we have to give you a boost in the base", and came up with a number that is about 40% less than what I am making in base salary now.

To top it off, she then asked me why I would leave my current position for one that paid 40% less. This got me a bit steamed. I told her that:

a) It was YOU who have been persuing me, not the other way around. I never said anything about wanting to leave my current position.

b) I would NEVER leave for 40% less, unless it was topped off by outright stock grants that would raise my total comp to a figure that was way over the base (something that they will not guarantee for this position).

c) I told her that I was an avid reader of the Mini-Microsoft blog (she said something like "Oh No!"), and that under the current conditions at Microsoft, I don't think that I would be interested in subjecting myself to that type of lifestyle. In addition, I was not interested in interviewing with some 25-year old pisher who would be asking me logic questions like "How Do You Move Mount Fuji?".

She asked me if I had any colleagues who would be interested, whereby I replied that all of my colleagues who might be interested were making a lot more money than you just offered. I told her that I would never consider at MS until there was evidence of a complete culture change and/or there was sustained upwards movement in the stock price. I told her that she should study Mini-Microsoft very carefully, and note the exodus from her her company.

What an amazing turnaround for the prestige of Microsoft, a company that I used to admire. I consulted for MS for 3 years back from 198901992, writing the first front end for SQL Server. My former MS manager is a group VP, and is a millionaire many times over. But, I am afraid that most of the bright lights there have now been dimmed.



©2006 Marc Adler - All Rights Reserved

What I am doing now

At my new client, one of the Tier-1 IBs on Wall Street, I am now in charge of a FX Exception Processing System. What this system does is allow FX Operations to examine and fix any FX trades which did not go through for one reason or another.

The front end is all C#/.NET, communicating with a Java trade engine using both Web Services and a home-grown XML message broker. Sybase is the database, and from the backend, connectivity is to both CLS and to SWIFTNet.

The GUI uses the Infragistics toolset, and is very grid-intensive. The real-time element is not crucial, and the trade volume is light enough so that we do not have to consider switching to the SyncFusion grid right now.

Any FX Trade Events (in this system, notification of a broken trade is called an 'event') that occur are sent from the backend to our GUI using the message broker. All FX Trades are also sent to our GUI. If the trade that comes in matches a filter criteria that is set up in one of the grids, then the trade is updated (or, in some events, the trade is deleted from the grid).

As more and more groups come on line and use our system, we will be runing into scalability issues. For example, let's say that you have a grid open that is monitoring all trades that occur today. Let's also say that no filtering criteria is set up, other than the fact that you want to look at today's trades. This means that every new trade will be inserted into the top of the grid. This is OK for now, as the trade volume is relatively light. But, more groups have expressed using our GUI. We anticipate that, by the end of the year, we might experience 10x the volume we have now.

I am going to be writing some stress-testing tools that will help us analyze the possible impact of other groups using our system. More on this later.

©2006 Marc Adler - All Rights Reserved

Comings and Goings

In the United States, men are glued to their TV sets, watching the National Football League's annual college draft. This is the time when 26 football teams throw a ridiculous amount of money at elite college atheletes.

On Wall Street, the annual post-bonus dance is almost complete. As people received their bonus checks in February or March, news comes almost every day that this person or that person has departed for company X or Y. This has dessimated several's company's IT departments, as the one person who knows a certain application inside and out is suddenly no more .... and the mad scramble for talent starts anew as companies try to backfill these positions.

(Wall Street is very small ... never burn your bridges.)

Just like the NFL draft, those of us in Wall Street IT sit back and await news to see where our colleagues end up. Such is the situation with me. I sit back and monitor the blogs, anxiously waiting to see where Matt, Pin, and Deglan end up. Matt announced his resignation on his blog, and invited all comers to bid on his services. In his last blog post, he said that he had many offers from his blog readers. Whoever the lucky company is who ends up with Matt, it will be money well spent.

The bar has been raised slightly in terms of compensation packages for senior developers. On Wall Street, a total compensation package of slightly over $200K is becoming more common. The calls from headhunters are becoming more frantic, as Wall Street scrambles to fill positions of their dearly departed developers. The base salary seems to still be $150K, but on Wall Street, bonus is everything. Managing Directors typically make 200-300% in bonus. Developers are still in the 30-40% range in most companies,except for the premier companies, where your 18-hour days might get you upwards of 80%. But, as a colleague of mine told me recently, many a marriage has been sacrificed in exchange for that bonus.

©2006 Marc Adler - All Rights Reserved

College Admissions

I just returned from a trip to California with my son. We have just started to look at colleges for him. He is a junior in high school, but this is when kids start considering colleges seriously. We went to see U Cal at Berkeley, Stanford, and Pomona. All three very different colleges.

Warning to parents: good grades and good standardized test scores just don't cut it anymore. Stanford rejects an awful lot of kids who get 1600's on their SATs. All of the colleges want to see rigorous courses in high school, great grades, great SAT I and SAT II and AP/IB scores. But they also want students that are unique in some way. The essays that kids have to write for their college applications are extremely important.

It is not only amazing difficult to get into the top-tier schools. It is also getting increasing difficult to get into the upper-middle tier schools. Applications are skewed by professional college counselors who you can hire for $10,000 to $30,000 .... you wonder if a kid gets into a certain college because of his/her own worth, or because daddy's paycheck is fat enough to hire a pro.

Now, we have to capture the one big intangible that my son has into an essay .. the fact that he is a leader ... not in the academic sense (ie: he is not the editor of the school newspaper nor the quarterback of his school's football team) ... but the fact that he has packs of kids that follow him around, that kids are constantly calling him and messaging him, that he can snap his fingers and a whole cadre of students will appear to schlep his drumset from gig to gig. In other words, someone who has that special magnetism that command attention amongst his peers (think Tony Soprano).

I wonder if Stanford is interested in the future leader of La Cosa Nostra.....

(To the British readers here .. does the same thing apply to Oxford and Cambridge? Is most of the UK clamoring to get into these two schools?)

©2006 Marc Adler - All Rights Reserved

Event Manager Code - Possible Enhancements

Now that I have posted the code for the Event Manager that I have used in several projects, I would like to list some possible enhancements that I have considered:

Precompile regular expressions
The Event Manager supports wildcards. The .NET RegularExpression classes are used to perform matching of a published topic with a wildcarded subscription. Howver, I do not pre-compile the regexps. This is a very simple change to make.

Enhanced regular expressions
We can expand the regular expressions that wildcarded subscriptions will accept. For example, to subscribe to an insert or delete action for a trade, we should be able to have a wildcard topic that looks like this:
Magmasystems.TradingSystem.Trade.[InsertedDeleted]

Stronger typing of args for event declarations
The third argument of EventManager.Fire() is anything that derives from EventManagerArgs. We can add more type safety by specifying the subclass of EventManagerArgs that a publisher expects to send and that the corresponding subscribers expect to receive.

Scoping
Microsoft's CAB has the notion of event scoping. We can limit a published event to subscribers that run in the same thread (or a certain thread) as the publisher. We can limit the scope to a named "applet". Otherwise, by default, the event is published globally.

EventManager.Register(this)
I am not totally thrilled with the fact that, for every object that publishes or subscribes, a call to EventManager.Register(this) is called. The Register() function will examine the passed class, using reflection on the class to build up a dictionary of publishers and subscribers to a topic.

Dynamically register the publisher and subscriber
Instead of using the static way of decorating a method, we may want to add publications and subscriptions dynamically. For instance, we should be able to say something liek this:

EventManager.Subscribe("Magmasystems.TradingSystem.Trade.*", this.OnTradeEvent);

Sinks for event publishing
Implement Sinks so a class can have a crack at an event args before it is sent to the subscribers.



©2006 Marc Adler - All Rights Reserved

Event Manager Code - EventManager.cs

Here is the code for the main EventManager class.

There are a number of ways that I would like to improve the code, but just never have had the time. When I get a few free moments, I will discuss some of the enhancements that I would like to put in the code eventually.

// for MethodImplAttrbute
using System;
using System.Collections;
using System.ComponentModel;
using System.Reflection;
using System.Runtime.CompilerServices;
using System.Text.RegularExpressions;
// for ISynchronizer

// --------------------------------------------------------------------
//
// This code is (C) Copyright 2005 Marc Adler
//
// --------------------------------------------------------------------

namespace Magmasystems.EventManager
{
  public delegate bool EventManagerEventHandler(object sender, string topicName, EventArgs e);

  public class EventManager
  {
    #region Delegates

    // Internal delegate used to help us fire async events
    private delegate void AsyncFire(Delegate del, object[] args);

    #endregion

    #region Variables

    // The singleton EventManager
    private static EventBroker _theEventManager = null;

    // A Dictionary of EventManagerEventInfo classes, indexed by the topic name
    private Hashtable _theEventDictionary = null;

    private Hashtable _theWildcardSubscribers = null;

    // Used to disabled and re-enable the firing of events
    private bool _isEnabled = true;

    #endregion

    #region Constructors and Static Instance

    protected EventBroker()
    {
    }

    // This is the way that the EventManager singleton is accessed
    static public EventManager Instance
    {
      get
      {
        if(_theEventManager == null)
        {
          _theEventManager = new EventBroker();
          _theEventManager._theEventDictionary = new Hashtable();
          _theEventManager._theWildcardSubscribers = new Hashtable();
          _theEventManager._isEnabled = true;
        }
        return _theEventManager;
      }
    }

    #endregion

    #region Properties

    private Hashtable Dictionary
    {
      get
      {
        // make sure that the dictionary and event manager are instantiated
        return _theEventDictionary;
      }
    }

    private Hashtable WildcardDictionary
    {
      get
      {
        // make sure that the dictionary and event manager are instantiated
        return _theWildcardSubscribers;
      }
    }

    public bool Enabled
    {
      get { return this._isEnabled; }
      set { this._isEnabled = value; }
    }

    #endregion

    #region General Methods

    static public void Register(object o)
    {
      Type type = o.GetType();

      MethodInfo[] methods = type.GetMethods();
      foreach (MethodInfo mi in methods)
      {
//        if(mi.DeclaringType != type)
//          continue;
        object[] oAttrs = mi.GetCustomAttributes(true);
        foreach (object oAttr in oAttrs)
        {
          EventManagerEventInfo evInfo;
          if(oAttr is EventSubscriberAttribute)
          {
            EventSubscriberAttribute evSubAttr = oAttr as EventSubscriberAttribute;
            evInfo = FindTopicEntry(evSubAttr.Topic, true);
            if(evInfo != null)
            {
              EventSubscriberInfo subInfo = evInfo.AddSubscriber(evSubAttr.Topic, o, evSubAttr.IsBackground, mi);
              if(subInfo.HasWildcards)
              {
                EventBroker.Instance._theWildcardSubscribers[evSubAttr.Topic] = evInfo;
              }
            }
          }

          else if(oAttr is EventPublisherAttribute)
          {
            EventPublisherAttribute evPubAttr = oAttr as EventPublisherAttribute;
            evInfo = FindTopicEntry(evPubAttr.Topic, true);
            if(evInfo != null)
            {
              evInfo.AddPublisher(evPubAttr.Topic, o);
            }
          }
        }
      }
    }

    static private EventManagerEventInfo FindTopicEntry(string topicName, bool createIfEmpty)
    {
      EventManagerEventInfo evInfo  ;

      topicName = topicName.ToUpper();
      object oEventInfo = EventBroker.Instance._theEventDictionary[topicName];

      if(oEventInfo == null)
      {
        if(createIfEmpty)
        {
          // Allocate a new entry
          evInfo = new EventManagerEventInfo();
          EventBroker.Instance.Dictionary[topicName] = evInfo;
        }
        else
        {
          evInfo = null;
        }
      }
      else
      {
        // Use the existing entry
        evInfo = oEventInfo as EventManagerEventInfo;
      }

      return evInfo;
    }

    #endregion

    #region Ways to Fire and Event

    [MethodImpl(MethodImplOptions.NoInlining)]
    static public void Fire(object sender, string topicName, EventArgs args)
    {
      if (EventBroker.Instance.Enabled == false)
        return;

      EventManagerEventInfo evInfo = FindTopicEntry(topicName, false);
      if(evInfo != null)
      {
        evInfo.Fire(sender, topicName, args);
      }

      foreach (object oKey in EventBroker.Instance._theWildcardSubscribers.Keys)
      {
        string keyName = oKey as String;
        Regex regExp = new Regex(keyName, RegexOptions.IgnoreCase);
        if(regExp.IsMatch(topicName))
        {
          evInfo = EventBroker.Instance._theWildcardSubscribers[oKey] as EventManagerEventInfo;
          evInfo.Fire(sender, topicName, args);
        }
      }
    }

    #endregion

    #region Inner Class for EventManagerEventInfo

    /// 

    /// EventManagerEventInfo
    /// This class represents information about a single event
    /// 
    public class EventManagerEventInfo
    {
      #region Variables

      // Multicast delegate of all subcribers to this event
      private event EventManagerEventHandler _eventHandler;

      // The list of classes that publish this event
      private ArrayList _publishers;
      // The list of classes that subscribe to this event
      private ArrayList _subscribers;

      #endregion

      #region Constructors

      public EventManagerEventInfo()
      {
        this._publishers = new ArrayList();
        this._subscribers = new ArrayList();
        this._eventHandler = null;
      }

      #endregion

      #region Events

      public event EventManagerEventHandler EventManagerEvent
      {
        add { this._eventHandler += value; }
        remove { this._eventHandler -= value; }
      }

      #endregion

      #region Properties

      public EventManagerEventHandler EventHandler
      {
        get { return this._eventHandler; }
      }

      public ArrayList Publishers
      {
        get { return this._publishers; }
      }

      public ArrayList Subscribers
      {
        get { return this._subscribers; }
      }

      #endregion

      #region Methods

      public EventSubscriberInfo AddSubscriber(string topicName, object objectRef, bool isBackground, MethodInfo mi)
      {
        EventSubscriberInfo subInfo = new EventSubscriberInfo(this, topicName, objectRef, isBackground, mi);
        this._eventHandler += new EventManagerEventHandler(subInfo.OnPublisherFired);
        this.Subscribers.Add(subInfo);
        return subInfo;
      }

      public EventPublisherInfo AddPublisher(string topicName, object objectRef)
      {
        EventPublisherInfo pubInfo = new EventPublisherInfo(this, topicName, objectRef);
        this.Publishers.Add(pubInfo);
        return pubInfo;
      }

      public void RemoveSubscriber(EventSubscriberInfo sub)
      {
        this.Subscribers.Remove(sub);
      }

      public void RemovePublisher(EventPublisherInfo pub)
      {
        this.Publishers.Remove(pub);
      }

      #endregion

      #region Event Firing

      public void Fire(object sender, string topicName, EventArgs args)
      {
        // This handles the event firing to the SubscriberInfo class. In turn, the
        // SubscriberInfo object will invoke the actual delegate. The SubscriberInfo
        // object will determine whether the delegate shoul dbe called synchronously
        // or asynchronously.
        if(this.EventHandler != null)
        {
          this.EventHandler(sender, topicName, args);
        }
      }

      #endregion
    }

    #endregion

    #region Inner class for EventPublisherInfo

    public class EventPublisherInfo
    {
      #region Variables

      private EventManagerEventInfo _evInfo;
      private WeakReference _objectRef;
      private string _topicName; // the upper-cased name
      private string _displayName; // used to generate context menus at runtime

      #endregion

      #region Constructors

      private EventPublisherInfo()
      {
        this._objectRef = null;
      }

      public EventPublisherInfo(EventManagerEventInfo evInfo, string topicName) : this()
      {
        this._evInfo = evInfo;
        this.DisplayName = topicName;
        this._topicName = topicName.ToUpper();
      }

      public EventPublisherInfo(EventManagerEventInfo evInfo, string topicName, object objectRef) : this(evInfo, topicName)
      {
        this._objectRef = new WeakReference(objectRef);
      }

      #endregion

      #region Properties

      public WeakReference Publisher
      {
        get { return (this._objectRef.IsAlive == true) ? this._objectRef : null; }
        set { this._objectRef = value; }
      }

      public string DisplayName
      {
        get { return this._displayName; }
        set { this._displayName = value; }
      }

      #endregion
    }

    #endregion

    #region Inner class for EventSubscriberInfo

    public class EventSubscriberInfo
    {
      #region Variables

      private EventManagerEventInfo _eventInfo; // ref back to the holding container
      private WeakReference _objectRef;
      private MethodInfo _methodInfo; // The method that the event firer should Invoke
      private bool _isBackground;
      private EventManagerEventHandler _delegateForAsync;

      private string _topicName; // we may have wildcards
      private bool _hasWildcards; // to help determine whether to use RegEx or not

      #endregion

      #region Constructors

      private EventSubscriberInfo()
      {
        this._objectRef = null;
        this._isBackground = false;
        this._hasWildcards = false;
      }

      public EventSubscriberInfo(EventManagerEventInfo evInfo, string topicName) : this()
      {
        this._eventInfo = evInfo;
        this.TopicName = topicName; // use the property so that formatting is done
      }

      public EventSubscriberInfo(EventManagerEventInfo evInfo, string topicName, object objectRef) : this(evInfo, topicName)
      {
        this._objectRef = new WeakReference(objectRef);
      }

      public EventSubscriberInfo(EventManagerEventInfo evInfo, string topicName, object objectRef, bool isBackground, MethodInfo mi) : this(evInfo, topicName, objectRef)
      {
        this._isBackground = isBackground;
        this._methodInfo = mi;

        if(isBackground)
        {
          this._delegateForAsync = (EventManagerEventHandler) Delegate.CreateDelegate(typeof (EventManagerEventHandler), objectRef, mi.Name);
        }

      }

      #endregion

      #region Properties

      public object Subscriber
      {
        get { return (this._objectRef.IsAlive) ? this._objectRef.Target : null; }
      }

      public bool IsBackground
      {
        get { return this._isBackground; }
        set { this._isBackground = value; }
      }

      public string TopicName
      {
        get { return this._topicName; }
        set { this._topicName = FormatTopicName(value); }
      }

      public bool HasWildcards
      {
        get { return this._hasWildcards; }
      }

      #endregion

      #region Methods

      private string FormatTopicName(string topic)
      {
        // We want to make things easy for matching publishers and sunscribers.
        // 1) We always use upper-case topic names.
        // 2) Replace the dots with slashes so that the dot is not taken as a regexp
        //    character by the pattern matcher.
        // 3) Let us know whether this topic has a wildcard in it so we know whether
        //    to use the slow regexp matcher or the faster Equals operator.
        if(topic.IndexOfAny(new char[] {'*'}) >= 0)
          this._hasWildcards = true;

        return topic.Replace('.', '/').ToUpper();
      }

      #endregion

      #region Event Firing

      /// 

      /// This gets called whenever the event manager fires an event.
      /// This does the hard work in event firing. It eventually calls
      /// the subscriber's delegate in order to process the event. it also determines
      /// whether the delegate should be called synchronously or asynchronously.
      /// 
      /// 
      /// 
      /// 
      /// 
      // 
      public bool OnPublisherFired(object sender, string topicName, EventArgs args)
      {
        // If the object that this subscriber is bound to has been garbage-collected, then
        // remove the subscriber from the EventInfo's subscriber list and return.
        if(this.Subscriber == null)
        {
          this._eventInfo.RemoveSubscriber(this);
          return true;
        }

        if(this.IsBackground)
        {
          AsyncFire asyncFire = new AsyncFire(InvokeDelegate);
          asyncFire.BeginInvoke(this._delegateForAsync, new object[] {sender, topicName, args}, new AsyncCallback(Cleanup), null);
        }
        else
        {
          object oRet = this._methodInfo.Invoke(this.Subscriber, new object[] {sender, topicName, args});
          if(oRet is Boolean)
            return (bool) oRet;
        }

        return true;
      }

      private void InvokeDelegate(Delegate del, object[] args)
      {
        ISynchronizeInvoke synchronizer = del.Target as ISynchronizeInvoke;
        if(synchronizer != null) // Requires thread affinity
        {
          if(synchronizer.InvokeRequired)
          {
            synchronizer.Invoke(del, args);
            return;
          }
        }

        // Not requiring thread afinity or invoke is not required
        del.DynamicInvoke(args);
      }

      private void Cleanup(IAsyncResult asyncResult)
      {
        asyncResult.AsyncWaitHandle.Close();
      }

      #endregion
    }

    #endregion
  }
}

©2006 Marc Adler - All Rights Reserved

Event Manager Code - EventManagerArgs.cs

These are two minor argument classes that are used to send information from the event publisher to the subscriber. The args are sent as the third parameter in the EventManager.Fire() function.

using System;

namespace Magmasystems.EventManager
{
 /// 

 /// Summary description for EventManagerArgs.
 /// 
 public class EventManagerArgs : EventArgs
 {
  public EventManagerArgs()
  {
  }
 }

        // This is used to pass string data between the publisher and subscriber
 public class EventManagerMessageArgs : EventManagerArgs
 {
  private string _message;
  
  public EventManagerMessageArgs(string msg)
  {
   this._message = msg;
  }

  public string Message
  {
   get { return this._message; }
  }
 }
}

©2006 Marc Adler - All Rights Reserved

Event Manager Code - EventSubscriberAttribute.cs

The EventSubscriberAttribute is used to decorate a C# function that is the recipient of a subscribed event from our event manager. The topic name can be a wildcard string, just like Tibco. For instance, to subscribe to all actions that happen to a trade, you can subscribe to topic "TradingSystem.Trade.*".

Notice that the attribute is declared with AllowMultiple=true. This lets a function have multiple subscription declarations.

The final thing to notice is the IsBackground flag. If a subscriber is declared with IsBackground=true, then the event will be dispatched to the subscriber on a worker thread (internally, Begin/EndInvoke is used).

Here is the code:

using System;

// --------------------------------------------------------------------
//
// This code is (C) Copyright 2005 Marc Adler
//
// --------------------------------------------------------------------

namespace Magmasystems.EventManager
{
 /// 

 /// EventSubscriberAttribute
 /// 
 [AttributeUsage(AttributeTargets.Method, AllowMultiple=true)]
 public class EventSubscriberAttribute : System.Attribute
 {
  private string _topicName;
  private bool   _isBackground;
    
  public EventSubscriberAttribute()
  {
  }

  /// 

  /// EventSubscriberAttribute
  /// 
  /// The name of the event
  public EventSubscriberAttribute(string topicName)
  {
   this._topicName    = topicName;
   this._isBackground = false;
  }
    
  public string Topic
  {
   get
   {
    return this._topicName;
   }
   set
   {
    this._topicName = value;
   }
  }

  public bool IsBackground
  {
   get
   {
    return this._isBackground;
   }
   set
   {
    this._isBackground = value;
   }
  }
 }
}

©2006 Marc Adler - All Rights Reserved

Event Manager Code - EventPublisherAttribute.cs

The EventPublisherAttribute is a C# attribute that decorates a function that publishes an internal event. Any function that publishes an event out to our little event broker should decorate itself with this attribute.For example:

[EventPublisher("Brokerage.TradingSystem.Trade.ReceivedFromBackend")]
public void OnTradeReceived(Trade trade)
{
  .......
  EventManager.Fire(this, "Brokerage.TradingSystem.Trade.ReceivedFromBackend", 
                    tradeArgs);
}

Here is the code:

using System;
// --------------------------------------------------------------------
//
// This code is (C) Copyright 2005 Marc Adler
//
// --------------------------------------------------------------------

namespace Magmasystems.EventManager
{
 /// 

 /// EventPublisherAttribute
 /// 
 public class EventPublisherAttribute : Attribute
 {
  private string _topicName;
  
  public EventPublisherAttribute()
  {
  }

  /// 

  /// EventPublisherAttribute
  /// 
  /// The name of the event
  public EventPublisherAttribute(string topicName)
  {
   this._topicName = topicName;
  }
  
  public string Topic
  {
   get
   {
    return this._topicName;
   }
   set
   {
    this._topicName = value;
   }
  }
 }
}

©2006 Marc Adler - All Rights Reserved

A Lightweight IntraApp Event Broker for C#/.NET

Over the years, I have managed to write a repository of interesting classes that has helped me in architecting and developing systems. Over the coming months, and as time allows, I will submit some of these classes for your use.

I wrote the EventBroker about two years ago for a trading system that had Tibco connectivity to a message bus that published quotes. I wanted a symmetrical processing model from the back end to the front end, and also, within the front end. So, I wrote a .NET/C#-based lightweight event broker that was like a min-Tibco within the GUI.

The Microsoft CAB has something similar, and when it came out, I took a few ideas from it (such as the handling of WeakReferences) and integrated it into my own Event Broker. CAB differs from mine in several respects .... namely, it has the concept of Event Scope, and it also has a different way of decorating code (it decorates event declarations, while mine decorates methods).

However, this event broker has been used in several trading systems and seems to function well.

In the next several posts, I will post the code of the Event Broker. You are free to use it as long as my copyright is maintained and proper acknowledgement is given. Also, I am anxious to hear of any improvments, enhancements and bug fixes you might make to any of the classes that I publish here. You can always reach me at magmasystems at yahoo dot com.

The Event Broker

The application uses a lightweight Publish/Subscribe (PubSub) model internally in order to notify the controller or UI layer of interesting events. A typical interesting event is a change in the underlying data model.

The mechanism that implements PubSub within the application is called the Event Broker. Event publishers and event subscribers will be automatically registered with the Event Manager by the use of customized .NET attributes.

The use of the Event Manager in no way precludes the application from doing its own event management using the standard .NET event/delegate mechanism.

Using the EventBroker in a class

Any class that wants to use the Pub/Sub capabilities of the EventBroker should do two thing.

1) Include a reference to the EventBroker's assembly. Also, reference the namespace within your class:

using Magmasystems.TradingSystem.EventManager;

2) Register the class with the EventBroker. A good place to do this is in the class' constructor. To register the class with the Event Broker, all that needs to be done is to put in the following line of code:

EventBroker.Register(this);

There are several .NET attributes that can be used to decorate functions in order to define them as either Event Publishers or Event Subscribers. When one of these attributes is constructed, the EventTopic parameter is examined. The EventTopic is added to the EventManager's internal Dictionary. A Dictionary collection is used in order to provide fast access to a particular Topic/Event pairing.

[EventPublisher(string EventTopic)]

This registers a function or class to be an event publisher. The class will publish an event with a specific name. Any subscribers to that topic will be notified.

[EventSubscriber(string EventTopic, options)]

This registers a subscriber to an event. The attribute should be placed directly above the function that will be used as the event handler. The options can be one of the following:
* Background - the handler is called asynchronously

The string-based topic name can be the actual name of a published topic, or it can be a wildcarded topic like "Magmasystems.TradingSystem.Trade.*".

To fire an event, the static method EventManager.Fire() is called

EventManager.Fire(object obj, string eventTopic, EventArgs args);

Event handlers have the signature:

public delegate bool EventManagerEventHandler(object sender,
string topicName, EventArgs e);


Here is a piece of code that publishes an event (The recipient could be a controller that processes events from views and from the models):


[EventPublisher("Magmasystems.TradingSystem.Controller.Action.GetTrades")]
private void GetTrades()
{
GetTradeArgs args = new GetTradeArgs();
args.CUSIP = "12345";
EventBroker.Fire(this, "Barcap.Gcdit.Odc.Controller.Action.GetTrades", args);
}

Here is a piece of code from a controller that subscribes to an event


[EventSubscriber("Magmasystems.TradingSystem.Controller.Action.GetTrades")]
public void GetTrades(object sender, string topicName, System.EventArgs e)
{
GetTradesUnitOfWork.GetTradesArgs args = e as GetTradesUnitOfWork.GetTradesArgs;
if (e == null)
return;

ExecuteAction(new GetTradesUnitOfWork(this._context.UIApplicationContext, args));
}


There is a .Net event associated with every topic that is registered. Events are really Multicast Delegates. Every subscriber to an event adds an event handler to the list of delegates. When an event is fired, the delegate list is traversed and each delegate will be invoked either synchronously or asynchronously. The options can include the Background flag. This tells the event firing mechanism that the underlying delegate should be invoked asynchronously. If the Background flag is not present in the attribute declaration, then the underlying delegate will be invoked synchronously.


Guidelines for Usage

Any class can publish an event, and any class can subscribe to that event. The event bus is global to the entire application.

The line of code that registers a class with the EventBroker is best put in the constructor of the Base Class.

Following our adoption of a namespace convention, we have also adopted a general naming convention for events. This convention is:

companyname.department.application.domainobject.action




©2006 Marc Adler - All Rights Reserved

Note To Self - Traversing Rows in a Single Band

I am not really a hardcore Infragistics person. I find it amazing that some of the features that I consider essential in their UltraWEBGrid offering are not found in their UltraWINGrid product.

I am writing a prototype of an app that has multiple levels of grouping. I need to be able to double-click on the column header of a band, and have it do something to only the rows in that band. For instance, if the user double-clicks on the column that says 'Selected', then I want every checkbox in that group to be toggled without affecting the rows in any other group.



Sounds easy, right? Find out which header you double-clicked on, and then get the child rows that are associated with that header. The problem is that headers are not considered true rows within UltraWinGrid. They are "UI Elements". They do not have references to the rows that are directly beneath them.

After a while of messing around with the HeaderDoubleClicked event, I finally decided to base my procesing off of the MouseDoubleClick event.

Here is what I finally came up with after a few hours of tinkering around. (By the way, the function 'ToggleSelected' is a good way of walking down the entire tree of rows in a grouped grid.)

private UltraGridRow m_firstRowOfTheHeaderThatWasDoubleClickedOn = null;

private void dgTrades_MouseDoubleClick(object sender, MouseEventArgs e)
{
  Infragistics.Win.UIElement element =
  this.dgTrades.DisplayLayout.UIElement.ElementFromPoint(new Point(e.X, e.Y));
  if (element != null)
  {
    this.CalcGridRowForDblClick(element);
    if (element is Infragistics.Win.TextUIElement)
    {
      HeaderBase hdr = element.GetContext(typeof(HeaderBase)) as HeaderBase;
      if (hdr != null)
        this.dgTrades_DoubleClickHeader(hdr);
    }
  }
}


private void dgTrades_DoubleClickHeader(HeaderBase hdr)
{
  if (hdr.Column.Key == "Selected")
  {
    if (this.m_firstRowOfTheHeaderThatWasDoubleClickedOn != null)
      this.ToggleSelected(e.Header, 
                          this.m_firstRowOfTheHeaderThatWasDoubleClickedOn);
  }

  this.m_firstRowOfTheHeaderThatWasDoubleClickedOn = null;
}



private void ToggleSelected(HeaderBase header, UltraGridRow row)
{
  if (row == null)
    return;
  
  UltraGridBand band = header.Band;
  UltraGridRow childRow = row.GetChild(ChildRow.First, band);
  if (childRow == null)
  {
    // May be a leaf node
    UltraGridColumn colSelected = band.Columns["Selected"];
    if (colSelected == null)
      return;
    int idx = colSelected.Index;
    for (; row != null; row = row.GetSibling(SiblingRow.Next, false))
    {
      row.Cells[idx].Value = !((bool)row.Cells[idx].Value);
    }
  }
  else
  {
    // Is a non-leaf node
    this.ToggleSelected(header, childRow);
    this.ToggleSelected(header, row.GetSibling(SiblingRow.Next, false));
  }
}


private UltraGridRow CalcGridRowForDblClick(Infragistics.Win.UIElement uiElement)
{
  this.m_firstRowOfTheHeaderThatWasDoubleClickedOn = null;
  
  if (uiElement == null)
  return null;

  object elementContext = uiElement.GetContext(typeof(UltraGridRow));
  if (elementContext == null)
    return null;

  UltraGridRow row = elementContext as UltraGridRow;
  if (row != null)
    this.m_firstRowOfTheHeaderThatWasDoubleClickedOn = row;
  return row;
}

It works. The key was the UIElement.GetContext() function, which I finally found by reading a two sentence Knowledge Base article on the Infragistics website.

©2006 Marc Adler - All Rights Reserved

RIP: Doug Walker (Alien Planetscapes)

Doug Walker, long-time mainstay of the New York Spacerock scene and founder of the band Alien Planetscapes, passed away Tuesday April 4th at home. Doug had a heart condition for several years, and it finally caught up to him.

Doug was one of my oldest friends. I met Doug in 1975, and played in several seminal free-jazz bands with him in the mid to late 70's, including the great Third Sun.

Doug lost his wife Fran 2 years ago in a horrific car crash.

Doug leaves behind his son Evan, who was born three weeks after my own son.

God Bless You, Doug. Now you can jam with Robert Moog.





©2006 Marc Adler - All Rights Reserved

What is the World Coming To?

First I take a full-time job, then DonXML does!

http://donxml.com/allthingstechie/archive/2006/03/20/2609.aspx

Don and I are moving in parallel paths. We have both found small consulting companies that are staffed with people that we respect. We both feel, and been given the opportunities, to make a difference in our companies and to help grow the business.

From what I remember, Don does not like to cross the Hudson River, so I will leave him to the NJ Pharma companies while I go after the Financials!


©2006 Marc Adler - All Rights Reserved

Rules of Engagement

My Expectations from a Client

My first engagement with Finetix has just ended, and it was an eye-opener in certain respects.

I have been thinking about what I would like to include in a retrospective to the client in order to help them manage future projects successfully. Instead of enumerating what I consider to be the positives and negatives of the project, I would like to add some of the aspects to my master “Lessons Learned” list, and also to reiterate some of my long-standing project-management processes.

1) Clearly Define Roles
2) Always Be Engaged
3) Make Sure Everyone Knows Everything
4) Define A Methodology And Stick To It
5) Have The Environment Completely Set Up
6) Have Documentation Ready
7) Engage the Business Analysts and Business Users
8) Do Not Pair-Program Unless Absolutely Necessary
9) Always Have a Roadmap For Refactoring


Clearly Define Roles

If you are bringing in consultants to lead the technical team, then tell your team members and enforce the leadership. If you are expecting your consultants to be short-term body-shoppers who are coding, then tell them this up front. Do not allow incorrect perceptions to pervade the group.

There will always be bruised feelings when you bring consultants on to a project in a leadership role. We consultants completely understand this. Nobody wants their work to be reevaluated and critiqued. If the consultants are being brought in to do rearchitecture, then they must be given the power to lead the effort.

Make it clear as to who holds the trump card.


Always Be Engaged

As a project manager, make sure that you know what all of your team members are doing, and make sure that all team members know what each other is doing. Make sure that the server side and client side teams communicate. Many server-side devs have also done GUI work and vice-versa.

If you have to support a legacy version of your product, then make sure that you are able to delegate that task to certain members of the team. Have a plan to get these “legacy developers” involved with the new development. The legacy devs are subject matter experts who are important to the whole team.


Make Sure Everyone Knows Everything

As mentioned above, do not isolate the groups. Involve the Business Analysts and Business Users where appropriate. Unless there are well-defined isolation layers, make sure that you try to completely define the communication layers and formats between the client and server. If the BA’s are planning something new, have them run it by the entire team so that the team can discuss the ramifications on the architecture.


Define A Methodology And Stick To It

If you are going to do Agile or Scrum, then stick to it. If you are going to do Waterfall, then stick to it. If you are going to decide on daily standups, then stick to it.


Have The Environment Completely Set Up

Consultants get paid a lot of money, and their efforts are usually time-boxed. So, make sure that they are productive from day one. Have all user accounts set up. Have all of the software ready. If this software requires additional registration, then make sure that this is done. Make sure that there are enough licenses for the software, and make sure that support packages have been purchased.

Make sure that the computers have enough memory and enough free disk space. Developers need about 2gb of RAM and about 100gb of free hard drive space. Make sure that certain shared drives can be accessed.

Make sure that the security people in the building know that a team is starting, and to expect them. If a consultant is made to wait in the lobby while security tries to track down someone to sign them in, then this serves nobody.


Have Documentation Ready

Does the system have documentation? Use cases? Architecture docs? If not, then either prepare them or prepare for a steeper learning process.


Engage the Business Analysts and Business Users

I have talked about this before. If you are writing a trading system, then the developers should be able to have access to the traders. The developers should be able to peek over a trader’s shoulder while he is working. The developers should have a complete feel for the kind of system that a trader would like to have.

If there are BAs that the developers must interact with, then make sure that the devs and BAs have constant interaction. Make sure that the BAs know if some of their ideas will be difficult to implement.


Do Not Pair-Program Unless Absolutely Necessary

I continue to abhor pair programming. I think that it cuts down productivity in a big way. I think that the best development is done when the developer is “in the zone”, and does not have to expend energy explaining every move to someone else.

Instead, have design meetings and developer meetings. It does not have to be “Big Design Up Front”. However, if a developer is architecting a crucial module, then let him present the design to the entire team and get critiques before the effort is too far gone.


Always Have a Roadmap For Refactoring

Do you know why a product is being refactored? Does the business absolutely need it? Do you really need to rewrite an entire application from scratch?

Remember that, when you refactor an application, you need a plan to retain all of the business logic that is built in to the existing app.

Make sure that the code has comments. Make sure that there is plenty of technical documentation. Make sure that all of the business rules are documented.

Make sure that all dead code has been eliminated from the application. It is difficult to rearchitect a system if the hands of 30 different people have been in it over the years.


These are my ideal Rules of Engagement for any project that I will be on, either as a leader or as a hired hand. I would love to hear your comments.


©2006 Marc Adler - All Rights Reserved

Transition #1

My last day in the land of the Freeborn is today. Good exposure to Credit Derivs.

Starting Monday at the home of the Big Mack. Enhancing an FX system.

©2006 Marc Adler - All Rights Reserved

Garden Leave

I rode on the train this morning with a neighbor who is a Managing Director at a Wall Street firm. He is switching companies, and just handed in his resignation. However, he does not start his new position for another 90 days.

It seems that most Wall Street companies are imposing a minimum number of days that you have to stay with a firm when you give your notice. In his case, he had to give 90 days notice. However, his current employer must pay him for the entire 90 days.

His current employer wants him out of the office as fast as possible, so that he does not have the chance to do any internal recruiting. So, he gets to sit at home for 3 months and collect a paycheck.

From what he told me, this practice has been prevalent in Europe, and is just starting to make the rounds in the United States. He told me that it is referred to as "Garden Leave", because the only thing you can do for 3 months is putt around in your garden.

©2006 Marc Adler - All Rights Reserved