I am having some trouble figuring out how to download and use xstream in eclipse. When I download the binary distribution from the website, I get a zip file. Where should I extract it, and how do I use it?
For the past two years I have been using RxJS extensively, in Cycle.js and in other contexts. Recently, TylorS and I have decided to build a new reactive streams library comparable to RxJS, called xstream.
In general, xstream is more suitable than RxJS when the number of subscribe() calls in an application is very small, and most of the logic is in the operator chain. On the other side, RxJS is more suitable than xstream when there are multiple calls to subscribe() of multiple Observables, or when RxJS is mixed with imperative programming, object-oriented programming and other diverse settings.
Our guideline was that a name should be a really strong hint towards the behavior of the operator. For instance the xstream operator remember() hints that the operator has some memory, it remembers something. In fact, it keeps in memory the most recently emitted event, and broadcasts that stored event to any newly added listener.
When we need to choose between terseness and readability, we choose the latter. For experienced programmers, the cost of typing a few more characters is at worst a first-world problem. If developers can understand code in xstream without reading the documentation, we will have accomplished our goals. Of course, we will test-drive the API with the community. So far we just have a good guess on what is an intuitive API.
We wanted to provide a smart default. xstream is under 30 kB in size, and it is ideal for using as a stream library in a driver. Cycle applications can still be written in RxJS v5, for instance, while utilizing a driver written in xstream.
I am still a core contributor and advocate of RxJS and will remain to be so. RxJS is a better option than xstream as a general-purpose library for reactive programming in the browser and in Node.js. In many ways it is more powerful than xstream, providing access to cold Observables (which are more generic than hot ones), schedulers (which xstream has none so far), marble diagram testing, and dozens of battle-proven operators. It is the ideal library to integrate with conventional imperative code and JavaScript.
confluence-compat-lib 1.4.2 has been released. This resolves an issue where the xstream-security module doesn't work correctly with the confluence-compat-lib in dev mode. Plugins can now use xstream-security module in atlassian-plugin.xml to mark the classes needed in XStream allowlist .
confluence-compat-lib 1.4.0 has been released to provide Backward-compatible code for plugins which want to keep a single version across all supported Confluence versions.
Plugins can utilise component com.atlassian.confluence.compat.setup.xstream.XStreamManagerCompat plugins. It can be initiated by way of Spring or manually with no-arg constructor XStreamManagerCompat(). See following for its signature:
Spring bean "xStreamManager" provides you ConfluenceXStream which is a wrapper around XStream but with the backward compatibility layer. confluenceXStream.toXML(obj) achieves you same results as xstream.toXML(obj). See:
When purchased separately, individual regulator stages remain as factory configured by the manufacturer and final integration must, out of necessity, become a customer responsibility.","status":"1","custom_stock_status":"59","hide_default_stock_status":"1","amxnotif_hide_alert":"0","request_path":"poseidon-xstream-1st-stage-black-g5-8","store_id":1,"category_id":"259","extension_attributes":,"tier_price_changed":0}; .product-image-container-6147 width: 240px;.product-image-container-6147 span.product-image-wrapper padding-bottom: 125%;prodImageContainers = document.querySelectorAll(".product-image-container-6147");for (var i = 0; i < prodImageContainers.length; i++) prodImageContainers[i].style.width = "240px";prodImageContainersWrappers = document.querySelectorAll( ".product-image-container-6147 span.product-image-wrapper");for (var i = 0; i < prodImageContainersWrappers.length; i++) prodImageContainersWrappers[i].style.paddingBottom = "125%"; Poseidon Xstream Black Second Stage 9/16 $399.95 window['JAJUMA_MATOMO_PRODUCT_DATA_ID_6147'] = "entity_id":"6147","attribute_set_id":"54","type_id":"simple","sku":"PDS-0120-010","has_options":"0","required_options":"0","created_at":"2016-05-26 23:39:52","updated_at":"2022-09-26 19:06:45","mst_search_weight":"0","mageworx_is_require":"0","price":"399.950000","tax_class_id":"2","final_price":"399.950000","minimal_price":"399.950000","min_price":"399.950000","max_price":"399.950000","tier_price":[],"reviews_count":"0","rating_summary":"0","is_salable":"1","absolute_price":"0","absolute_cost":"0","absolute_weight":"0","hide_additional_product_price":"0","dependency_rules":"[]","hidden_dependents":"\"hidden_options\":[],\"hidden_values\":[],\"preselected_values\":[]","sku_policy":"use_config","cat_index_position":6,"name":"Poseidon Xstream Black Second Stage 9\/16","small_image":"\/p\/d\/pds-0120-010_1a.jpg","thumbnail":"\/p\/d\/pds-0120-010_1a.jpg","url_key":"poseidon-xstream-black-second-stage-9-16","swatch_image":"no_selection","short_description":"Poseidon 2nd Stage Xstream Black 9\/16.","product_restriction":"When purchased separately, individual regulator stages remain as factory configured by the manufacturer and final integration must, out of necessity, become a customer responsibility.","status":"1","custom_stock_status":"59","hide_default_stock_status":"1","amxnotif_hide_alert":"0","request_path":"poseidon-xstream-black-second-stage-9-16","store_id":1,"category_id":"259","extension_attributes":,"tier_price_changed":0; "[data-role=tocart-form], .form.map.checkout": "catalogAddToCart": WARNING Poseidon does not endorse the installation or substitution of any non-factory part or component with their products because they do not have the ability to control or evaluate the quality and compatibility of such items. The installation of non-factory parts such as regulator hoses or other components may or may not have negative effects upon performance, function and safety. Poseidon disclaims liability for defect, damage or injury caused by the use of any non-factory parts or accessories. Upstream vs Downstream The demand valves found in scuba second stages can be either upstream or downstream design. In a downstream valve, the moving part of the valve opens in the same direction as the flow of gas and is kept closed by a spring. In an upstream valve, the moving part works against the pressure and opens in the opposite direction as the flow of gas. The upstream design is less likely to experience problems caused by wear and more resistant to free flow, but most scuba second stages are downstream design. If the first stage fails and delivers excessive pressure to the second stage, a downstream valve is forced open resulting in a free flow and rapid loss of breathing gas. With an upstream valve, the result of over pressurization usually means the valve is forced closed. This will stop the free flow but unless the over pressure is relieved it may cause another failure such as a hose rupture or loss of buoyancy control. This means that regulators with upstream second stages must always incorporate an over pressure relief valve (OPV) in their design. The OPV allows the diver to continue to breathe the regulator with a minimal loss of gas.
Set xstream.allowlist.enable sysprop to true. This is equivalent to XStream 1.4.18 behaviour and it exist in Confluence 7.10 and up. But it comes with a risk of broken third-party plugins which have not yet configured xstream-security module with their classes. Confirm with Third-party plugin vendors before toggling it if your Confluence instance uses a third-party plugin and it relies on XStream.
aa06259810