[Asterisk-Dev] Manager header revision

[mattf]

I guess maybe I'm thinking(from several of the threads I've read) that the
new manager interface is going to be radically different from the current
manager interface. So much so that it would be very hard to port existing
apps to use the new interface without completely redesigning them as well.

What I will probably end up doing if the new manager is radically
different(unless someone else does it first) is just making a proxy script
that serves some limited scope of Actions and translates them into new
Manager queries and then outputs the old-format outputs back out.

So you can ignore my request for backward-compatibility, it is always much
easier to move forward when you aren't trying to pull a large rock behind
you.

What are some of the mistakes you would blame on the current Manager
interface?

MATT---




-----Original Message-----
From: Brian West [mailto:brian.west at mac.com]
Sent: Monday, April 04, 2005 4:03 PM
To: Asterisk Developers Mailing List
Subject: Re: [Asterisk-Dev] Manager header revision


Why?  Backwards compatibility == Same mistakes.

/b

On Apr 4, 2005, at 10:17 AM, mattf wrote:

> I would very much like to keep the ability to maintain
> backwards-compatibility(at least for the first affected Release) in a
> module-type fashion so that it could be disabled to improve performace 
> or
> enabled to allow compatibility for all of the apps that have been 
> developed
> to work with it to date.
>
> What is the timeframe/release scope that this manager redo is under?
>
> MATT---
>
> -----Original Message-----
> From: William Suffill [mailto:william.suffill at gmail.com]
> Sent: Monday, April 04, 2005 10:57 AM
> To: Asterisk Developers Mailing List
> Subject: Re: [Asterisk-Dev] Manager header revision
>
>
> Agreed. The Manager Interface seems to need the most work. I guess
> starting from scratch would be the most productive and perhaps keep
> backwards compatibility on a proxy level or not at all. It would
> become a mess if we try to move forward and still keep the old junk
> along for the ride.
>
> -- William
> _______________________________________________
> Asterisk-Dev mailing list
> Asterisk-Dev at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-dev
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev
> _______________________________________________
> Asterisk-Dev mailing list
> Asterisk-Dev at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-dev
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev

_______________________________________________
Asterisk-Dev mailing list
Asterisk-Dev at lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-dev
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev