web-meetme-devel — Developers discussion

[Web-meetme-devel] Time for a 2.1.0 release?

[Dan A. <Dan...@Ph...>]

I've got the current SVN code running on three internal servers,
and so far almost everything is working as expected.

I've started to prepare for 1.4, but that will require/result
in a number of changes not exactly compatible with 1.2.  I'd
like to cut a release with the latest fixes and features before
moving forward.

Plans for Asterisk 1.40-
	*  Update app_cbmysql to new loader mechanism
	*  Integrate new meetme options
		*  Improved mute/unmute logic
		*  meetme list concise (reduce monitor parser
complexity)

Also on the ToDo list is to try to get cbEnd.php to work better
than it does currently.  It now seems to tolerate Asterisk restarting,
but I've had one case where a large number of perticipates left a
conference at the same time, and cbEnd hung, using 99% of system
CPU.

So, any objections to a release?

Dan

Re: [Web-meetme-devel] testing

[Areski <ar...@gm...>]

As you can see from Benchmarks the AdoDB is much efficient than Pear
http://phplens.com/lens/adodb/

and honestly it takes few minutes to migrate as they have some method with
the same name in order to facilitate the pear-adodb migration.

We did it 3 weeks ago for A2Billing and it's worth it :D

Rgds, Areski

On 6/14/06, Dan Austin <Dan...@ph...> wrote:
>
> Dan Austin wrote:
> >  Don't sweet it.  I've been coding like a mad man, as a recent
> > upgrade here finally killed the proprietary conferencing platform
> > we were using.  That basically forced management to let me deploy
> > Asterisk and Web-MeetMe.  The response internally has been excellent,
> > and goaded me into adding a number of planned features.
> >
> > I've found a couple of issues that involve your code that I could
> > not determine the best way to proceed.
> >
> > 1.  _SESSION['userid'] vs _SESSION['username']
> >       You have both, but the code seems to prefer userid, except
> >       for displaying the conference owner.  The easiest fix would
> >       be for LDAP authentication to set both, but I'm not clear on
> >       why both are needed.
>
> > This is probably bad coding on my part. I can review the latest code
> to
> > make it consistent and eliminate the unneeded one (probably
> 'username'.
> > This is related to me eliminating the need for a text username and
> > simply using email addresses for login.
> I started to convert the LDAP code to userid, but stopped when I saw you
> had both.  There is only a couple of instances left in the svn tree.
>
> > 2.  The direct MySQL queries.
> >       I really like the functionality you added using them, and
> >       I've done the same in a couple of new features, but this breaks
> >       the database agnostic approach, and likely ends support for
> >       postgres.  While I don't use postgres, I think we should try
> >       to maintain the flexibility.
>
> > I thought I used the PEAR DB libraries which support MySQL, PostgreSQL
>
> > and several othe DBs.I find those routines much easier to read and
> > understand than what was being used. Another option is ADODB. I have
> > never used that abstarction library, but understand it is more
> efficient
> > than the PEAR routines. It does support all the major RDBMSes.
> >
> You may have.  I did not notice any new libraries, and was not really
> focused on them, so I might have missed them.
>
> > Oh, and I just added a redirect on my home server to point people
> > looking for the package to SF and saw the stats jump quite a bit.
> >
> Thanks,
>
> Mike
>
>
> _______________________________________________
> Web-meetme-devel mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/web-meetme-devel
>
>
> _______________________________________________
> Web-meetme-devel mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/web-meetme-devel
>


-- 
--
    ~     - Belaid Arezqui ( ar...@gm... )
   'v'    - Cell Phone. : (+34) 650 78 43 55  (Spain, GMT+1hr)
  // \\
 /(   )\  - CHAMELEON FAITH HEALER
  ^`~'^   - http://www.areski.net - http://asterisk2billing.org/
_______________________________________________
-- To support Asterisk2Billing - paypal account : in...@ar...

Re: [Web-meetme-devel] Realtime MeetMe

[Dan A. <Dan...@Ph...>]

 I've been waiting for 1.4 to settle down.  I had hoped that someone
with
more experience in the Asterisk code would tackle the first pass, and
then
I could help, but the RealTime effort for MeetMe appears to have
stalled.

Dan

-----Original Message-----
From: web...@li...
[mailto:web...@li...] On Behalf Of
Mike Clark
Sent: Tuesday, June 13, 2006 7:35 PM
To: Web...@li...
Subject: [Web-meetme-devel] Realtime MeetMe

Dan:

Any new developments on the RealTime MeetMe front? That sure would be
nice.


Mike


_______________________________________________
Web-meetme-devel mailing list
Web...@li...
https://lists.sourceforge.net/lists/listinfo/web-meetme-devel

Re: [Web-meetme-devel] testing

[Dan A. <Dan...@Ph...>]

=20
Dan Austin wrote:
>  Don't sweet it.  I've been coding like a mad man, as a recent
> upgrade here finally killed the proprietary conferencing platform
> we were using.  That basically forced management to let me deploy
> Asterisk and Web-MeetMe.  The response internally has been excellent,
> and goaded me into adding a number of planned features.
>=20
> I've found a couple of issues that involve your code that I could
> not determine the best way to proceed.
>=20
> 1.  _SESSION['userid'] vs _SESSION['username']
> 	You have both, but the code seems to prefer userid, except
> 	for displaying the conference owner.  The easiest fix would
> 	be for LDAP authentication to set both, but I'm not clear on
> 	why both are needed.

> This is probably bad coding on my part. I can review the latest code
to=20
> make it consistent and eliminate the unneeded one (probably
'username'.=20
> This is related to me eliminating the need for a text username and=20
> simply using email addresses for login.
I started to convert the LDAP code to userid, but stopped when I saw you
had both.  There is only a couple of instances left in the svn tree.

> 2.  The direct MySQL queries.=20
> 	I really like the functionality you added using them, and=20
> 	I've done the same in a couple of new features, but this breaks
> 	the database agnostic approach, and likely ends support for
> 	postgres.  While I don't use postgres, I think we should try
> 	to maintain the flexibility.

> I thought I used the PEAR DB libraries which support MySQL, PostgreSQL

> and several othe DBs.I find those routines much easier to read and=20
> understand than what was being used. Another option is ADODB. I have=20
> never used that abstarction library, but understand it is more
efficient=20
> than the PEAR routines. It does support all the major RDBMSes.
>=20
You may have.  I did not notice any new libraries, and was not really=20
focused on them, so I might have missed them.

> Oh, and I just added a redirect on my home server to point people
> looking for the package to SF and saw the stats jump quite a bit.
>=20
Thanks,

Mike


_______________________________________________
Web-meetme-devel mailing list
Web...@li...
https://lists.sourceforge.net/lists/listinfo/web-meetme-devel

[Web-meetme-devel] Realtime MeetMe

[Mike C. <mik...@wp...>]

Dan:

Any new developments on the RealTime MeetMe front? That sure would be nice.


Mike

Re: [Web-meetme-devel] testing

[Mike C. <mik...@wp...>]

Dan Austin wrote:
>  Don't sweet it.  I've been coding like a mad man, as a recent
> upgrade here finally killed the proprietary conferencing platform
> we were using.  That basically forced management to let me deploy
> Asterisk and Web-MeetMe.  The response internally has been excellent,
> and goaded me into adding a number of planned features.
> 
> I've found a couple of issues that involve your code that I could
> not determine the best way to proceed.
> 
> 1.  _SESSION['userid'] vs _SESSION['username']
> 	You have both, but the code seems to prefer userid, except
> 	for displaying the conference owner.  The easiest fix would
> 	be for LDAP authentication to set both, but I'm not clear on
> 	why both are needed.

This is probably bad coding on my part. I can review the latest code to 
make it consistent and eliminate the unneeded one (probably 'username'. 
This is related to me eliminating the need for a text username and 
simply using email addresses for login.

> 2.  The direct MySQL queries. 
> 	I really like the functionality you added using them, and 
> 	I've done the same in a couple of new features, but this breaks
> 	the database agnostic approach, and likely ends support for
> 	postgres.  While I don't use postgres, I think we should try
> 	to maintain the flexibility.

I thought I used the PEAR DB libraries which support MySQL, PostgreSQL 
and several othe DBs.I find those routines much easier to read and 
understand than what was being used. Another option is ADODB. I have 
never used that abstarction library, but understand it is more efficient 
than the PEAR routines. It does support all the major RDBMSes.
> 
> Oh, and I just added a redirect on my home server to point people
> looking for the package to SF and saw the stats jump quite a bit.
> 
Thanks,

Mike

Re: [Web-meetme-devel] testing

[Dan A. <Dan...@Ph...>]

 Don't sweet it.  I've been coding like a mad man, as a recent
upgrade here finally killed the proprietary conferencing platform
we were using.  That basically forced management to let me deploy
Asterisk and Web-MeetMe.  The response internally has been excellent,
and goaded me into adding a number of planned features.

I've found a couple of issues that involve your code that I could
not determine the best way to proceed.

1.  _SESSION['userid'] vs _SESSION['username']
	You have both, but the code seems to prefer userid, except
	for displaying the conference owner.  The easiest fix would
	be for LDAP authentication to set both, but I'm not clear on
	why both are needed.
2.  The direct MySQL queries.=20
	I really like the functionality you added using them, and=20
	I've done the same in a couple of new features, but this breaks
	the database agnostic approach, and likely ends support for
	postgres.  While I don't use postgres, I think we should try
	to maintain the flexibility.

Oh, and I just added a redirect on my home server to point people
looking for the package to SF and saw the stats jump quite a bit.

Dan

-----Original Message-----
From: Mike Clark [mailto:mik...@wp...]=20
Sent: Tuesday, June 13, 2006 2:18 PM
To: Dan Austin; Web...@li...
Subject: Re: [Web-meetme-devel] testing

Dan Austin wrote:
> SF claims that the mail list issues have been resolved.....
>=20
>=20
> _______________________________________________
> Web-meetme-devel mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/web-meetme-devel
>=20

Dan:

Just shoot me. I apologize for not getting back sooner. Things have been

crazy lately. I did get your prior emails. I will review tonight at the=20
hotel and reply. I am just completing a major IVR project, so I hope my=20
schedule will be opening up more over the next few weeks.

Mike

Re: [Web-meetme-devel] testing

[Mike C. <mik...@wp...>]

Dan Austin wrote:
> SF claims that the mail list issues have been resolved.....
> 
> 
> _______________________________________________
> Web-meetme-devel mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/web-meetme-devel
> 

Dan:

Just shoot me. I apologize for not getting back sooner. Things have been 
crazy lately. I did get your prior emails. I will review tonight at the 
hotel and reply. I am just completing a major IVR project, so I hope my 
schedule will be opening up more over the next few weeks.

Mike

[Web-meetme-devel] testing

[Dan A. <Dan...@Ph...>]

SF claims that the mail list issues have been resolved.....