asterisk users - Mar 2007 - Re: Asterisk Java w/ Threads

With Asterisk-Java the proposed solution to connect to multiple Asterisk
servers is to create multiple AsteriskManagerConnection obeject.
Each ManagerConnection handles its own thread so there is no need for
custom thread handing code.
All you have to do is to make sure is the EventListener objects you pass
to these connections synchronize access to shared data (if there are
such accesses).
I think this approach is rather simple for the user and don't see a
benefit in adding a proxy to that picture.

=Stefan

-- 
reuter network consulting
Neusser Str. 110
50760 Koeln
Germany
Telefon: +49 221 1305699-0
Telefax: +49 221 1305699-90
E-Mail:  stefan.reuter@reucon.com
Jabber:  stefan.reuter@reucon.com

Steuernummern 215/5140/1791 USt-IdNr. DE220701760

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 252 bytes
Desc: OpenPGP digital signature
Url :
http://lists.digium.com/pipermail/asterisk-users/attachments/20070305/bc19ec20/signature.pgp

Stefan Reuter wrote:
> With Asterisk-Java the proposed solution to connect to multiple Asterisk
> servers is to create multiple AsteriskManagerConnection obeject.
> Each ManagerConnection handles its own thread so there is no need for
> custom thread handing code.
> All you have to do is to make sure is the EventListener objects you pass
> to these connections synchronize access to shared data (if there are
> such accesses).
> I think this approach is rather simple for the user and don't see a
> benefit in adding a proxy to that picture.
In the past, the Asterisk Manager Interface was prone to crashes if it 
had more than 1 client connected to it.  The proxy solved that issue.  I 
think this issue was resolved in 1.2.