Skip to main content

Response on OverSim

Thanks everyone for the encouraging words on my OverSim tutorials. I got several positive blog comments & direct e-mails. It's seems time is right for a more formal tutorial. I'll try to expand the existing topics & add new ones within next couple of weeks. Please contribute by sending sample codes & suggestions that will help all of us.

Comments

John Gilmore said…
Hi,

I really enjoyed your Oversim blog and would really appreciate that tutorial :-)

I'm working with a network of Super peers and Peers and thus I require two churn generators. The problem I'm currently having is that two types of terminals still seem to be connected to the same overlay.

I only want the super peers connected to the overlay and the peers only connected via UDP/TCP.

Regards
John
Dilum Bandara said…
Sorry, I don't have any idea on how to overcome your issue. I personally believe OverSim (in its current state) is not good for simulating superpeer or other hierarchical systems.

Popular posts from this blog

1. Building P2P Simulators with OverSim - Where to Begin

This could be a series of blog posts about extending or developing your own OverSim applications & overlay networks. OverSim has a minimal tutorial on writing your own application & overlay network; however, it doesn't show the big picture. So, I'm wasting lots of time playing with code & trying to understand the rest. Good thing is, I like it more & more as I understand. You need to change/develop only a few things, but finding out which ones is a hell of a task. I hope this will not only make my life easy but also will be useful to new comers. Here's what you need to do: You need some background on OMNeT++ OverSim extend OMNeT++. But sometime it has its own way of doing things (to make your task even simple) so understand the differences . Develop several OMNeT++ simulators. TicToc is a good one to start with. Extend it as you imagine. Read Towards a Common API for Structured Peer-to-Peer Overlays , which is the basis for OvseSim's AP...

Distributed Systems Mind Map

Though distributed systems are inherently distributed, autonomous, and parallel, all textbooks that I have read so far are boring & serial, going from one topic to another as they are independent topics. Wondering about how best to present all related topics and their relationships in my class, I came up with the following mind map. I was able to explain most of the key concepts using a single example of a web-based business that started selling flowers. It was a student who suggested that we consider selling flowers. It turned out to be a good example, as there had to be a connection to the physical world where the business also needed a geographical distributed delivery system. Taught of sharing the mind map. Though most of those branches can be broken down further this level of detailed was sufficient for my class (by the way it took 1 hour to finish the discussion on this slide). Distributed Systems Mind Map

Small Basic for biginners

Microsoft recently introduced Small Basic, a programming language for beginners. It's a strip down version of BASIC with only 15 key words. It seems to be a fun programming environment & definitely worth while trying. You can write both console & graphical interface enabled programs & even develop your own version of Logo. Some of the features include: Its free 15 key words that support basic programming concepts including conditions & iterations Intellisense & context sensitive help Define variables on the fly, no need to explicitly define them Graphic programming Subroutines Third-party libraries can be plugged, API is given It even comes with a simple but comprehensive user guide that introduce basic programming concepts & Small Basic. Though it's intended for beginners, even advanced develops can use it to write scripts that perform simple day to day tasks.