Cocoa software design issue
Cocoa software design issue
- Subject: Cocoa software design issue
- From: "Devraj Mukherjee" <email@hidden>
- Date: Tue, 9 May 2006 11:05:09 +1000
Hi Everyone,
I am writing some tools for OSX to work with the open source PBX
called Asterisk. For those interested the source code will be
available on http://sf.net/projects/astrxtools4osx/
At this stage I have a Cocoa framework that all application share, the
framework is reponsible for speaking the Asterisk Manager protocol
with the server and presents the applications with a Objective-C style
API to talk to the Asterisk server.
The socket connection is established everytime the user initiates an
event. A login process is carried out everytime and the
socket/connection is destroyed at the end of the request execution.
Obviously with the increasing number of application using this
framework I will face the following issues
1. The socket being created and destroyed each time an event occurs
2. To handle advanced functionality initiated by the Asterisk server
the socket has to be kept open.
The ideal solution would be to create a single socket connection to
the Asterisk server and write somewhat of a proxy that the
applications can then talk to. This will also enable me to handle call
backs.
My questiions are as following:
1. Can I do this using a framework?
2. Can frameworks be instantiated once and all applications use a shared copy?
3. Or else, how do I go about writing daemon styled applications in Cocoa?
Thanks for your time
Devraj
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden