- 浏览: 1561069 次
- 性别:
- 来自: 北京
文章分类
- 全部博客 (571)
- Flex (301)
- AIR (5)
- ComPiere (8)
- ExtJS (15)
- SAP (0)
- jBPM (3)
- Java-Hibernate (5)
- Java-Spring (10)
- XML (2)
- java-web (30)
- db2 (2)
- websphere (4)
- Google (5)
- 虚拟机 (10)
- eclipse (8)
- Win2003 (11)
- Ubuntu (27)
- VMware (4)
- CentOS (3)
- JSON (1)
- Oracle (15)
- SilverLight (1)
- 大事记 (6)
- VirtualBox (5)
- Solaris (10)
- AIX (6)
- 云计算 (10)
- MacOS (4)
- iOS (1)
- SQLite (1)
- Activiti (1)
- jdk (5)
- hadoop (8)
- Ant (4)
- PhoneGap (2)
- JavaScript (11)
- jQuery (1)
- FireFox (1)
- HBase (2)
- sqoop (0)
- ffmpeg (7)
- mencode (0)
- jdbc (1)
- SQLServer (1)
- 组件平台 (12)
- struts2 (4)
- intellj (4)
- android (1)
- ExtJS4 (1)
- 色卡司 (1)
- Linux (3)
- ExtJS5 (1)
- zookeeper (2)
- maven (1)
- Java (6)
- vpn (0)
- squid (1)
- MySQL (2)
- webpackage (1)
- antd (1)
- lucene (1)
最新评论
-
qq_24800465:
请问这里的库从哪下载啊
ffmpeg所有的编码器(encoders) -
neusoft_jerry:
貌似这里没用到StreamingAMFChannel哦,只是用 ...
Flex BlazeDS 推送技术 -
anyone:
感谢你的博文,看了受益匪浅
记住这个IntelliJ IDEA的编译设置 -
keren:
现在还有什么应用需要用flex来开发的?
flex tree的展开,关闭,添加、删除子节点 -
neusoft_jerry:
简洁明快,好贴好贴!楼主V5!
flex tree的展开,关闭,添加、删除子节点
http://www.insideria.com/2009/02/lcds-data-push-subscription-sc.html
If you have ever worked with LiveCycle Data Services or BlazeDS in a data-broadcast (data-push) scenario, there's no doubt know about using Consumer objects to receive streams of data. When messages are received, MessageEvent.MESSAGE events are dispatched, and your application can respond to the incoming data as it is received.
If you are working with subscription based scenarios (meaning that you only want to receive specific messages based on some sort of criteria), there are a few things that you can do.
And no, receiving all messages on every client, and handling them as a client side filter is not a good solution.
【Selector based filtering】
One option that you can do is to use the selector property on a consumer object. The selector property allows you to build filters that resemble a SQL where clause.
myHeader > 0 OR myHeader < 10
These filters examine the headers of each message coming from the LCDS server, and are filtered on the server-side. Messages that do not fulfill the subscript filter are not sent to the client.
Reducing the number of messages sent to each client reduces network bandwidth utilization and increases throughput. Selector filters are created on the client, and can be changed at any time during the life of a Flex application.
The drawback with this approach is that it is expensive and potentially insecure. It is expensive in that every message coming through the LCDS messaging bus needs to have its headers examined, and it loops through all subscribed consumers to see if it should be sent to that consumer. Put thousands of messages per minute into this scenario, with thousands of consumers, and it will back up eventually, and it is not fun to debug.
It is potentially insecure in that if you subscribe to that messaging channel without specifying a selector, then you get every message coming across the messaging channel. If you are working with sensitive data, this could be an issue.
【Subtopics】
Rather than using a selector property, you can also filter messages coming through a messaging channel using subtopics. When you connect, you connect to a specific subtopic, and any messages that are not within that subtopic are not sent to the consumer instance. There can be many subtopics per messaging channel, and subtopic message delivery is much faster on the server side. Subtopics provide a filtering mechanism similar to that of selectors where messages are filtered on the server side, however they are much faster, as there is a direct mapping of subtopic and subscribed consumers. The "expensive" analysis of a selector query does not need to be executed for each consumer instance. Instead, each message is directly routed to the appropriate consumer based on mappings in-memory in the LCDS instance.
Subtopics are also more secure than selector queries because if you subscribe to a messaging channel without specifying a subtopic (and incoming messages have a subtopic specified) then you will not receive any messages from the server.
Each message can only have one subtopic, however you can subscribe to multiple suptopics using a MultiTopicConsumer component. MultiTopicConsumers are used in the same manner as "regular" Consumer objects, except that they are able to subscribe to more than one subtopic per messaging channel. This is very helpful in broadcast scenarios.
Think about a real-time stock tracking application -- Your server is dispatching messages for each stock symbol. For this example, let's just examine "ADBE", "GOOG" and "MSFT". You only want to receive messages for "ADBE" and "MSFT". There can be a subtopic for ADBE, and a subtopic for MSFT. With a "regular" Consumer object, you would only be able to subscribe to one. With a MultiTopicConsumer, you could subscribe to incoming messages on both the ADBE and MSFT subtopics. This approach enables each individual client connection to subscribe for a different set of updates on different subtopics -- essentially providing the same capability as a selector filter of stockSymbol='ADBE' or stockSymbol='MSFT', execpt that it is faster and more secure.
If you have ever worked with LiveCycle Data Services or BlazeDS in a data-broadcast (data-push) scenario, there's no doubt know about using Consumer objects to receive streams of data. When messages are received, MessageEvent.MESSAGE events are dispatched, and your application can respond to the incoming data as it is received.
If you are working with subscription based scenarios (meaning that you only want to receive specific messages based on some sort of criteria), there are a few things that you can do.
And no, receiving all messages on every client, and handling them as a client side filter is not a good solution.
【Selector based filtering】
One option that you can do is to use the selector property on a consumer object. The selector property allows you to build filters that resemble a SQL where clause.
myHeader > 0 OR myHeader < 10
These filters examine the headers of each message coming from the LCDS server, and are filtered on the server-side. Messages that do not fulfill the subscript filter are not sent to the client.
Reducing the number of messages sent to each client reduces network bandwidth utilization and increases throughput. Selector filters are created on the client, and can be changed at any time during the life of a Flex application.
The drawback with this approach is that it is expensive and potentially insecure. It is expensive in that every message coming through the LCDS messaging bus needs to have its headers examined, and it loops through all subscribed consumers to see if it should be sent to that consumer. Put thousands of messages per minute into this scenario, with thousands of consumers, and it will back up eventually, and it is not fun to debug.
It is potentially insecure in that if you subscribe to that messaging channel without specifying a selector, then you get every message coming across the messaging channel. If you are working with sensitive data, this could be an issue.
【Subtopics】
Rather than using a selector property, you can also filter messages coming through a messaging channel using subtopics. When you connect, you connect to a specific subtopic, and any messages that are not within that subtopic are not sent to the consumer instance. There can be many subtopics per messaging channel, and subtopic message delivery is much faster on the server side. Subtopics provide a filtering mechanism similar to that of selectors where messages are filtered on the server side, however they are much faster, as there is a direct mapping of subtopic and subscribed consumers. The "expensive" analysis of a selector query does not need to be executed for each consumer instance. Instead, each message is directly routed to the appropriate consumer based on mappings in-memory in the LCDS instance.
Subtopics are also more secure than selector queries because if you subscribe to a messaging channel without specifying a subtopic (and incoming messages have a subtopic specified) then you will not receive any messages from the server.
Each message can only have one subtopic, however you can subscribe to multiple suptopics using a MultiTopicConsumer component. MultiTopicConsumers are used in the same manner as "regular" Consumer objects, except that they are able to subscribe to more than one subtopic per messaging channel. This is very helpful in broadcast scenarios.
Think about a real-time stock tracking application -- Your server is dispatching messages for each stock symbol. For this example, let's just examine "ADBE", "GOOG" and "MSFT". You only want to receive messages for "ADBE" and "MSFT". There can be a subtopic for ADBE, and a subtopic for MSFT. With a "regular" Consumer object, you would only be able to subscribe to one. With a MultiTopicConsumer, you could subscribe to incoming messages on both the ADBE and MSFT subtopics. This approach enables each individual client connection to subscribe for a different set of updates on different subtopics -- essentially providing the same capability as a selector filter of stockSymbol='ADBE' or stockSymbol='MSFT', execpt that it is faster and more secure.
发表评论
-
extjs结合flex(flash)的注意事项.
2014-01-02 17:11 2399//for fix bug //flash里使 ... -
flash(flex)crossdomain dtd规范
2013-12-27 13:38 954dtd文件位置: http://www.macromedia. ... -
flash内嵌在html里面的代码
2013-12-27 09:19 1197<!-- 除IE外都可识别 --> < ... -
FlashBuilder4.5 ADT命令详解(官方)
2011-12-16 17:45 1255http://help.adobe.com/en_US/air ... -
FlashBuilder4.5加入ADT插件
2011-12-16 17:24 1811参考: http://renaun.com/blog/2011 ... -
Flex as3commons log的简单使用
2011-11-28 20:26 1597http://www.as3commons.org/ &l ... -
Flex日志工具汇总
2011-11-27 16:29 1251巨兽 monster [能调试 mobile和web air] ... -
【转】[Flex]我经常使用的Flex Tools 和 Resource
2011-11-22 08:36 1310http://www.k-zone.cn/zblog/post ... -
[转]Flex Socket安全策略<policy-file-request/>及应对方法
2011-08-27 16:43 1730http://hi.baidu.com/dobodo/blog ... -
flash 安全策略文件
2011-08-27 16:31 2152<?xml version="1.0&qu ... -
Request请求头的格式
2011-08-27 15:38 2364每次提交http请求时,请求头是什么样的的格式呢? GET方 ... -
flash Tooltip类
2011-08-27 15:06 1141http://www.flepstudio.com/flash ... -
flash SQLite包装类
2011-08-27 15:00 2234[转]http://www.flepstudio.com/fl ... -
[转](原创)flex解决跨域问题的策略文件的写法
2011-08-04 09:59 1560http://hi.baidu.com/wosinmaiken ... -
[转](整理)flex常用验证控件
2011-08-04 08:30 1387http://hi.baidu.com/wosinmaiken ... -
Flex4.5 skin组建皮肤的应用
2011-07-28 08:52 2817http://www.iyoya.com/2011/06/04 ... -
如何成为一个合格的iOS开发者?
2011-07-17 14:59 1349转:http://www.adobe.com/cn/devne ... -
flex4.5移动设备开发-添加应用背景图片
2011-07-17 10:50 2293【转】http://spy6.blogspot.com/201 ... -
flex4.5移动设备开发-应用访问权限设置
2011-07-16 14:19 1361在构建flex4.5 mobile application的时 ... -
flex4.5移动设备开发-表格效果
2011-07-15 23:12 1806做了个实验,没想到做出表格的效果
相关推荐
elipse下配置的spring+flex+blazeds,进行消息推送,还加入了了quarz定时策略。希望对大家有帮助。
blazeDS是FLEX和Java通信的信息机制的消息处理机制
NULL 博文链接:https://lxlkulong.iteye.com/blog/1135716
基于Java_BlazeDS_Flex_服务器消息推的聊天室 了解BlazeDS推送机制,flex调用java web BlazeDS的过程 服务器推,摒弃ajax的轮询,减轻服务器压力!
BlazeDS是一个基于服务器的Java远程调用(remoting)和Web消息传递(messaging)技术,使得后台的Java应用程序和运行在浏览器上的Flex应用程序能够相互通信。
Flex + blazeds + Java推送Demo 本例实现由Flex一端客户端发送消息, 然后由Java端在发布到所有订阅的其它Flex端. 里面有说明与源码, 还有一个直接放到Tomcat里面的直接发布的项目 小编使用工具 eclipse3.5 flex sdk...
Flex技术本身和Java就有很强的关联性,它提供了一个基于Eclipse的IDE和BlazeDS.BlazeDS是个基于服务端的Java远程调用和Web消息的一个开源的技术。有许多应用都是以Java为后端处理的。Flex用于前端。由于Java和Flex...
BlazeDS通信到Java的PureMVC——Flex框架,BlazeDS的服务器配置比较麻烦,这里使用的是直接下载blazeds_turnkey_3-0-0-544.zip中的tomcat BlazeDS模板路径为: blazeds_turnkey_3-0-0-544.zip解压后路径\tomcat\...
Using BlazeDS and Flex integrated。
使用BlazeDS实现Java和Flex通信
blazeds.war blazeds
最简单的BlazeDS实现flex与java通信..无积分下载...最简单的BlazeDS实现flex与java通信..无积分下载...最简单的BlazeDS实现flex与java通信..无积分下载...最简单的BlazeDS实现flex与java通信..无积分下载...最简单的...
一个blazeds的eclipse工程的消息推送的例子,导入就可以运行例子
blazeds4整合spring3 这是我新近研究的方法 与整合spring2.5以下的方法有不同了,(看过一些教程觉得不是很好,用起来不顺手) 最终参考了官方的sample,得到了这个不错的整合方法。 把要用blazeds公开给flex的java...
Spring BlazeDS Integration,Flex通过remoteObject与java通讯,附带例子 文档
包含blazeds.war blazeds-spring.war 以及解压后的blazeds,blazeds-spring文件夹, 可直接拷贝到javaee项目下的WebRoot文件夹下
BlazeDS入门:HTTP Service BlazeDS入门:HTTP Service BlazeDS入门:HTTP Service
Blazeds入门教程.doc
blazeDS war包及Flex结合blazeDS的入门程序及操作步骤比较适合入门选手
RT 已经含有了blazeDs.war FlashBuilder4 Tomcat6下测试通过~ 先启动后台服务 http://localhost:8080/Flex4JavaDemo/TickCacheServlet?cmd=start http://localhost:8080/Flex4JavaDemo/message.html