Bruce,
None of the options you have would work for serious production
application unless you invest heavily in making the client and server code
more reliable. Please keep in mind that once you go that route you are on
your own for data traffic robustness and performance.
I would try to see if you can scale application in any other way - 4 core
single CPU and removal all business functionality to different servers is
always an option. You might get even better scalablity by going RTMP
route or provide pseudo-connectivity wrapper using non-blocking IO via
client - proxy - LCDS - Messaging - LCDS - proxy -client pish.
Regards,
Anatole
On 10/16/07, Bruce Hopkins <[EMAIL PROTECTED]> wrote:
>
> Yeah, I'm using HTTPService right now with E4X results. The for large
> data results, however, XML is not desirable.
>
> I'd prefer to use some framework that uses AMF3 in order to get more
> compact results.
>
> Bruce
>
> On 10/16/07, Jeff Schuenke <[EMAIL PROTECTED]> wrote:
> >
> > You can also just use HTTPService to do direct HTTP requests. I am
> > using this for communications with a JAVA backend.
> >
> > --- In [email protected] <flexcoders%40yahoogroups.com>, "Bruce
> > Hopkins" <[EMAIL PROTECTED]>
> >
> > wrote:
> > >
> > > Hi all,
> > >
> > > All I want to do is have my Flex client to communicate with my Java
> > backend.
> > > Due to licensing restrictions, LCDS won't be an option for us. So
> > far the
> > > biggest contenders are:
> > >
> > > 1. Granite Data Services
> > > 2. OpenAMF
> > > 3. WebORB
> > > 4. Red5
> > >
> > > Does anyone have any strong opinions, suggestions, or biases on
> > either of
> > > these solutions?
> > >
> > > Thanks,
> > >
> > > Bruce
> > >
> >
> >
>
>
