woensdag 17 februari 2010

Event System

I started bare work on an event system. Currently you always had to retrieve ALL downloads / nodes / searches (in the old version that is)

Now a client can subscribe for events, as simple as this:

RemoteAPI.RegisterEvents(RemoteAPI.EventType.NodeChange);

Then you can poll for events using for example this

var nodeEvents = RemoteAPI.GetNodeEvents();

This will clean any events that were stored as well.

This event-cache is per-client so multiple client can subscribe, and by getting the events, they will only clear their own basket.

Update 4:26

I finished the first part of my events : it now works for all outgoing node connections.

Here some NEW screenshots from the new client using the new efficient event system instead of retrieving all connections each time!

image Connections! Wooh!

image

 

 

 

 

 

 

 

 

 

 After clicking Outgoing (so it is unchecked)

imageAfter clicking Outgoing (so it is checked again)

As you can see, the times didn’t update, I noticed and fixed it :)

Geen opmerkingen:

Een reactie posten