|
I have a stand alone application (messenger). I was asked to the messenger to have the fallowing possibility:
from a link with a phone number parameter to make a call in the application. If the messenger is not installed, to take the client to the official web site. If the product is installed to see if it is open. If it is open and the user is logged in to make the call.
My idea is the client to check the registry and see if the product is there, which solves the first part. If there are certain keys in the registry next step is from the processes to see if the product is active. If active somehow send instruction to call the function : CallNumber( phonenumber phnum)
Can you give me any leads on how to do all this, any other solution to the task?
The project is done in C++
Thank you very much
Dimkov Trajce
|
|
|
|
|
What??? What legitimate reason do you have for dialing a number? Possibly without the user knowing that you have done so.
Programs that have done this in the past have been used to hijack users phonelines and redirect them to premium rate numbers (often abroad).
Please explain what the legitimate reason is to do this.
|
|
|
|
|
I am developing the application, and it is a messenger who has voip.
The company asked me if users can make phone calls using the messenger from a link on a web page with the phone number as a parameter. If some security is needed i can implement it in the application, and the link they will get only after signing in on the official webpage.
Extra difficulty is if they erase the the messenger. This is the reason why I have to see if the application is in the computer(if so but closed to ask to open the application) and if the application is by some chance removed, (it is not in the registry my guess) take the user on the official download site.
I believe something like this can be done with scripting on the client side code with javascript, but I am not sure
|
|
|
|
|
If they erase the messenger and you want to take them to the official webpage, then you wouldn't want to dial the number. You would just use something like
Process.Start("http://www.mycompany.com"); from the application.
|
|
|
|
|
let me split this to couple of questions:
1.Can I access the registry with IE and if yes how?
2. Can I use IE and scripting language to call a program with parameter?
Thank you Pete in advance
|
|
|
|
|
Directly, you can't access the registry. The way that I've done this in the past was to have an external C routine called from a Java applet running in the browser session.
|
|
|
|
|
I decided to create an ActiveX commponent which will find the application by PID.
If it doesn find the PID, the app is not running, if yes Ill do ::SendMessage to the window of the app
|
|
|
|
|
Please visit my blog and add your comments and feedbacks for the discussion topic I have raied on "Evolving Software Architectures in CRM world".
http://pchaitanya.wordpress.com
Chaitanya
|
|
|
|
|
Hi all
I am new to the area of "software architecture" . Could anyone please provide me links/books and subjects to look for to know about the job of an architect ?
redindian
|
|
|
|
|
If your very new, then start with Patterns, I prefer to start with Head First Design Patterns and go with GOF( Gang of Four) Patterns by Erich Gama
And you know the Road to go ahead.
Regards,
Vythees
|
|
|
|
|
I disagree. Architects are responsible of programming in the large, whereas DESIGN patterns are standard solutions to solve problems in programming in the small (as the design in the name already says).
And a side note:
Yes, yes I know there is no clear boundary between architecture and design, no need to write that to me 
-^-^-^-^-^-
no risk no funk
|
|
|
|
|
You need to understand your client's needs, technology to archieve their needs, and design a solution of their needs.
"Throughout human history, we have been dependent on machines to survive. Fate, it seems, is not without a sense of irony. " - Morpheus
"Real men use mspaint for writing code and notepad for designing graphics." - Anna-Jayne Metcalfe
|
|
|
|
|
|
Almost any application in our company interacts with data sources. As the number of applications and data sources grows it becomes very difficult to support our information system. To avoid this we decided to develop some "common gateway" - middle tier that will be used by all applications that need to access any data sources. Also we plan to implement WCF for this task.
What do you think about this?
Does anybody know any existing solutions?
Thanks.
|
|
|
|
|
I don't have an answer for you but a question:
A single "gateway" will surely simply the "layout" of your system (applications, data sources, ...) but will probably introduce a bottleneck, because all applications have to communicate with this gateway.
When performance is critical then a more SOA like approach (not exactly sure if SOA is the right term, though) by building a system where services interact on there own. When each service has a clearly defined task then this approach is clearer and more scalable then a Gateway approach.
But it's very difficult to give a perfect solution for all possible systems
-^-^-^-^-^-
no risk no funk
|
|
|
|
|
“A single "gateway" will surely simply the "layout" of your system (applications, data sources, ...) but will probably introduce a bottleneck, because all applications have to communicate with this gateway. “
Our test application, built on WCF processes about 200 client requests per second. Average number of rows returned for one request is about 100. Hardware – is our oldest server based on 2 CPU’s Pentium3. It does not seem to me to be a bottleneck.
“When performance is critical then a more SOA like approach (not exactly sure if SOA is the right term, though) by building a system where services interact on there own. When each service has a clearly defined task then this approach is clearer and more scalable then a Gateway approach.”
If we take the approach where a numerous services will interact on there own and will have a clearly defined task –there will be almost the same problems that we have now: different applications (or services) will access different data sources at anyway they like. At the same time “Gateway approach” provides the full control over interaction with data sources – very useful in case of finding bugs or performance issues. This approach also gives an opportunity to implement some kind of “business layer” –that will be common for all developers.
I consider WCF to be the perfect platform for building SOA-oriented applications. So “Gateway” is not necessary the “one” and “only” service in the information system. If there will be some central repository, where the elements of business logic will be held – we can use any number of this “Gateway” services according to our needs.
|
|
|
|
|
You almost convinced me, but one last concern:
With a single gateway you risk to get a monolythic solution (everything is stuffed into one place).
What do you plan to prevent this? How to you keep good extensibility and maintainability?
-^-^-^-^-^-
no risk no funk
|
|
|
|
|
For this reasons (performance, security,maintainability) we can use several instances of services. They can share common repository or have it's own. Besides data sources these services will be able to communicate with each other or any external web or wcf-services.
In general we are going to achieve extensibility and maintainability by using some common model of business logic that will accommodate our needs.
|
|
|
|
|
After reading the other posts, too, I think that you have a nice concept for your solution. Reminds me somewhat of CAB (Composite UI Application Block) where the CAB is the central part that coordinates all others, just like your Gateway coordinates DataSources and client applications.
Best luck with your approach. And maybe you can provide us with some information how it worked out in a CodeProject article - would be very interesting.
-^-^-^-^-^-
no risk no funk
|
|
|
|
|
I think you should see this: www.datumnode.com
|
|
|
|
|
Thanks for the interesting link.
-^-^-^-^-^-
no risk no funk
|
|
|
|
|
The way I think:
You need a data provider factory, which returns an IDataSource. Any new DataSource provider would be implement the IDataSource. Once you have a default implemention (base class) of the the IDataSource, you could effectively use the provider pattern to return the datasource.
Effectively, the client would talk with the factory to return the appropriate data source provider.
Now, how you talk with the factory host, could be decided on the performance, deployment plans, ease of applying updates etc. A simple webservice hosting the above mentioned factory should get your started ?
But again, it does not sound like a good idea to have one webservice datasource provider for all the applications you use unless its the same datasource which is being used.
|
|
|
|
|
With this “gateway” we plan to implement some kind of business logic – that will be common to all developers. In this case, not only “data sources will be the same” but developers will even have no idea with what database they are actually interacting with.
|
|
|
|
|
rokford wrote: To avoid this we decided to develop some "common gateway" - middle tier that will be used by all applications that need to access any data sources. Also we plan to implement WCF for this task.
I don't think I understand. You are going to run all queries and result sets through the gateway machine?
|
|
|
|
|
Not machine but by common service (or services).
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
