Thanks Robert, it worked.
On Sun, Jun 13, 2010 at 6:23 PM, Robert Kern wrote:
> On Sun, Jun 13, 2010 at 20:10, Vishal Rana wrote:
> > Robert,
> > There is no error on python side but on flex client which
> > is "Channel.Call.Failed" faultDetail="NetConnection.Call.Failed: HTTP:
> > Status 503"
On Sun, Jun 13, 2010 at 20:10, Vishal Rana wrote:
> Robert,
> There is no error on python side but on flex client which
> is "Channel.Call.Failed" faultDetail="NetConnection.Call.Failed: HTTP:
> Status 503"
> Here is the documentation for type mapping flex vs
> python: http://pyamf.org/architectur
Robert,
There is no error on python side but on flex client which is "*Channel*.*
Call*.*Failed*" faultDetail="NetConnection.Call.Failed: *HTTP*: Status 503"
Here is the documentation for type mapping flex vs python:
http://pyamf.org/architecture/typemap.html, pyamf takes python data types so
I a
On Sun, Jun 13, 2010 at 19:52, Vishal Rana wrote:
> I created a record array (from strings and floats) with no dtype defined as:
> ra = np.core.records.fromrecords(sq_list, names=("a", "b", "c"))
> ra.a is found to be of type numpy.float64, when I serialize it using pyamf
> under Mac OS X it works
I created a record array (from strings and floats) with no dtype defined as:
ra = np.core.records.fromrecords(sq_list, names=("a", "b", "c"))
ra.a is found to be of type numpy.float64, when I serialize it using pyamf
under Mac OS X it works great but under ubuntu 10.04 it fails. Looks like
serial
