Question
Feature requests for Flash Media Server 3
Hello Adobe FMS dev team :)
Who i must contact in the Adobe FMS dev team to indicates a whish list
of all new features and fix bug i want in the next version of FMS ?
For the moment for example my feature requests for FMS3 are :
http://groups.google.com/group/vegasos/browse_thread/thread/45bad8e9be51d40a
1 - Use a Javascript 1.7 or 1.8 core Engine with E4X, Generator,
Iterator, etc.
2 - class mapping with no anonymous class
for the moment we can use class mapping only with anonyme function, i
would like register a class with a namespace :
{{{
namespace = {} ;
namespace.myConstructor = function()
{
}
application.registerClass( "myConstructor" ,
namespace.myConstructor ) ;
}}}
For the moment FMS send the error message :
Sending error message: Error registering class: line name mismatch
(myConstructor, anonymous): name mismatch (myConstructor,
anonymous).
3 - class mapping with complexe ids to register the class :
{{{
function MyConstructor()
{
}
application.registerClass( "test.myConstructor" , MyConstructor ) ;
}}}
For the moment FMS send the error message :
Sending error message: Error registering class: line name mismatch
(test.myConstructor, MyConstructor): name mismatch
(test.myConstructor, MyConstructor).
4 - Server side byteArray, int, uint; Dictionnary... same type in AS3.
5 - FMS console with debug level mode based on the mx.logging package
and AIR external console.
6 - Server side SQLite DB api (like AIR API)
7 - mail() method to send mail server side.
With this list i can enumerate some problem and bugs in FMS2 for the
moment and i hope the next FMS version fix this bugs !
For me i think more interesting to see in the labs of adobe a FMS wiki
page and an issue list to creates tickets proposals :)
EKA+ :)
Who i must contact in the Adobe FMS dev team to indicates a whish list
of all new features and fix bug i want in the next version of FMS ?
For the moment for example my feature requests for FMS3 are :
http://groups.google.com/group/vegasos/browse_thread/thread/45bad8e9be51d40a
1 - Use a Javascript 1.7 or 1.8 core Engine with E4X, Generator,
Iterator, etc.
2 - class mapping with no anonymous class
for the moment we can use class mapping only with anonyme function, i
would like register a class with a namespace :
{{{
namespace = {} ;
namespace.myConstructor = function()
{
}
application.registerClass( "myConstructor" ,
namespace.myConstructor ) ;
}}}
For the moment FMS send the error message :
Sending error message: Error registering class: line name mismatch
(myConstructor, anonymous): name mismatch (myConstructor,
anonymous).
3 - class mapping with complexe ids to register the class :
{{{
function MyConstructor()
{
}
application.registerClass( "test.myConstructor" , MyConstructor ) ;
}}}
For the moment FMS send the error message :
Sending error message: Error registering class: line name mismatch
(test.myConstructor, MyConstructor): name mismatch
(test.myConstructor, MyConstructor).
4 - Server side byteArray, int, uint; Dictionnary... same type in AS3.
5 - FMS console with debug level mode based on the mx.logging package
and AIR external console.
6 - Server side SQLite DB api (like AIR API)
7 - mail() method to send mail server side.
With this list i can enumerate some problem and bugs in FMS2 for the
moment and i hope the next FMS version fix this bugs !
For me i think more interesting to see in the labs of adobe a FMS wiki
page and an issue list to creates tickets proposals :)
EKA+ :)
