Ë verdade!!
Então, tem tanta funcionalidade que eu tenho que parar e ver certinho quando
eu posso usar.
Para vc ter idéia, olha os tipos de channel que ele disponibiliza:
<channels>
<channel-definition id="my-streaming-amf"
class="mx.messaging.channels.StreamingAMFChannel">
<endpoint
url="http://{server.name}:{server.port}/{context.root}/messagebroker/streamingamf";
class="flex.messaging.endpoints.StreamingAMFEndpoint"/>
</channel-definition>
<channel-definition id="my-amf"
class="mx.messaging.channels.AMFChannel">
<endpoint
url="http://{server.name}:{server.port}/{context.root}/messagebroker/amf";
class="flex.messaging.endpoints.AMFEndpoint"/>
<properties>
<polling-enabled>false</polling-enabled>
</properties>
</channel-definition>
<channel-definition id="my-secure-amf"
class="mx.messaging.channels.SecureAMFChannel">
<endpoint
url="https://{server.name}:{server.port}/{context.root}/messagebroker/amfsecure";
class="flex.messaging.endpoints.SecureAMFEndpoint"/>
</channel-definition>
<channel-definition id="my-polling-amf"
class="mx.messaging.channels.AMFChannel">
<endpoint
url="http://{server.name}:{server.port}/{context.root}/messagebroker/amfpolling";
class="flex.messaging.endpoints.AMFEndpoint"/>
<properties>
<polling-enabled>true</polling-enabled>
<polling-interval-seconds>4</polling-interval-seconds>
</properties>
</channel-definition>
<channel-definition id="my-http"
class="mx.messaging.channels.HTTPChannel">
<endpoint
url="http://{server.name}:{server.port}/{context.root}/messagebroker/http";
class="flex.messaging.endpoints.HTTPEndpoint"/>
</channel-definition>
<channel-definition id="my-secure-http"
class="mx.messaging.channels.SecureHTTPChannel">
<endpoint
url="https://{server.name}:{server.port}/{context.root}/messagebroker/httpsecure";
class="flex.messaging.endpoints.SecureHTTPEndpoint"/>
</channel-definition>
<channel-definition id="per-client-qos-polling-amf"
class="mx.messaging.channels.AMFChannel">
<endpoint
url="http://{server.name}:{server.port}/{context.root}/messagebroker/qosamfpolling";
class="flex.messaging.endpoints.AMFEndpoint"/>
<properties>
<polling-enabled>true</polling-enabled>
<polling-interval-millis>500</polling-interval-millis>
<flex-client-outbound-queue-processor
class="flex.samples.qos.CustomDelayQueueProcessor">
<properties>
<flush-delay>5000</flush-delay>
</properties>
</flex-client-outbound-queue-processor>
</properties>
</channel-definition>
</channels>
+)
Atenciosamente:
-------------------------------------------------------
| Rodrigo Pereira Fraga |
http://www.digows.com
e-mails: [EMAIL PROTECTED]
[EMAIL PROTECTED]
-------------------------------------------------------
--------------------------------------------------
From: "João Fernandes" <[EMAIL PROTECTED]>
Sent: Tuesday, January 08, 2008 11:02 AM
To: <flexdev@googlegroups.com>
Subject: [flexdev] Re: GraniteDS Vs BlazeDS
>
> A grande diferença que eu vejo entre o BlazeDS e o GraniteDS é que não
> so permite data push por polling mas também por um novo canal de
> HTTPStreaming semelhante ao RTMP mas que funciona por HTTP.
> --
>
> João Fernandes
>
> http://www.onflexwithcf.org
> http://www.riapt.org
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
Você recebeu esta mensagem porque está inscrito na lista "flexdev"
Para enviar uma mensagem, envie um e-mail para flexdev@googlegroups.com
Para sair da lista, envie um email em branco para [EMAIL PROTECTED]
Mais opções estão disponíveis em http://groups.google.com/group/flexdev
-~----------~----~----~----~------~----~------~--~---
