I'm trying to design a custom component architecture for development environment of our interpreted language. However, I've stucked on defining scopes of control over those custom components. Since this is a client-server system,the codes interpreted on server side and results are sent over network to the client for rendering/updating. All controls and variables have a representation on server side as symbols having different level of scopes.

Moreover, the system is already matured upto some level without having custom component concept and feature. So how this re-factoring and re-engineering process should be and how the custom component architecture design should be


Ekrem Aksoy


Re: Architecture General Custom Component Architecture


Ekrem, can you be more specific on the problem you are trying to solve I (for one) can't seem to grasp the the issue. Thanks!

Re: Architecture General Custom Component Architecture



Think we have a client-server framework. This framework has an interpreted language. On the client side, we have dialogs and controls designed with our development environment. The system works like you fire some action from client side , then corresponding code is run at serverside. Only thing sent over network is the control's new states (e.g. values, attributes, etc.). By the way, there is application scope (which a sequence or workflow of dialogs structure), class scope (the class scope defined by functions in a class)

My intention is to create a custom component architecture, in which you can develop your own custom components having their own scope, local symbols and so on. And, by nature of concept, the only way of communication with "outside" is events and properties. Now I'm trying some concepts. And, I decided to consult my best advisor, MSDN :) So indeed, there is no problem but just a design issue.

Re: Architecture General Custom Component Architecture


I advise you to look at ASP.Net component architecture, you just need something similar.
ASP.Net uses special naming to find, load and populate the controls. This is exactly what you need to do
but as I have understood, it should be on the client side.