Changed content should set the archive bit, but whether or not that tells the search "crawler" to re-index, I have to admit I have no idea - actually, that's probably only meaningful to an archive application, like backup.
Sep 23, 2015 at 8:24PM
All of the above makes link aggregation for multiple ISPs must be prohibitively expansive even if they can offer it. I can't think of reason how normal people can be allowed for have it (except maybe for special servers like the DNS roots which are the basis of modern internet).
I'm still not convinced that multiple ISPs can implement aggregation directly, as each ISP would only be getting part of an aggregated connection - i.e. who does the remote host (which know nothing of your aggregation arrangements) return a response to?
To do aggregation you need a single aggregation routing point - either a single ISP with multi-link connections, or a service beyond the ISP, such as the example of SharedBand, which can manage the aggregation and split the traffic over multiple ISP connections, using it's routing knowledge provided by the multi-homed client router.
Given the way the world is moving, their focus is on Office 365, and making sure that they win new iOS and Android users. I can think of a few times it would have been nice to have this support, but generally most businesses have found alternatives, and Microsoft's eggs are in developing cross platform.
We use Outlook because we run Exchange, Dynamics-CRM and a 3rd-party SIP PBX, and there are Outlook add-ins that provide tight integration of all three, as well as X-Server functionality.
The PBX is on-prem, and we have data regulatory conditions and internet performance limitations that require the Dynamics data stay on-prem... and because Exchange and Dynamics don't function well in hybrid config (one on-prem the other in-cloud) this means Exchange also has to stay on-prem. So having an Outlook client that rendered HTML properly would be nice.
Presumably, because they are still dithering about over what is their rendering technology going forward... the deprecated IE11 engine or the half-baked Edge engine.
Sep 23, 2015 at 2:35PM
I don't believe you can do aggregation using BGP to multiple ISPs, as each ISPs is then routing end-point and can't "re-assemble" the multiplexed packets, of which it only sees some. The best you can do is to analyse your traffic and split the load on the multiple links using policies, and configure the traffic for each link failover to the other.
However, there are aggregation services available, such as this:
Sep 22, 2015 at 11:09PM
You can do multi-link aggregation to a single ISP (and there are plenty of ISPs that offer multi-link PPP etc) but I don't think you can do multi-link aggregation across multiple ISPs (or even different connection services at the same ISP) as both routing end-points need to be able to control the multiplexing of the aggregated traffic.
However, there are aggregation services available, that allow you to use multiple ISPs. Typically, you have a specially configured router, that allows you to connect your various ISP connections, and then all traffic is encapsulated and routed to the aggregation provider, who then re-routes the traffic to the original destination - and vice-versa. You can lose an ISP connection, and just lose it's part of the total aggregation bandwidth. However, you can't mix/match different types of services - e.g. all must be DSL.
Sep 20, 2015 at 3:18PM
if you want to have a non-changing ip then you need to request an address block from the iana (if I recall the right name) and they do not hand them out unless you can justify why you need an assignerd subnet. then you can just do whjat any isp does to have more than one backbone connected to a router with bgp and assigned netblocks .... but then you are not going to be able to do this cheap you just became a peer on the internet and will need to buy some kind of dedicated circuit from each backbone provider who will carry traffic for you.
Yep - If having a single IP with failover from multiple ISPs is the aim, then the IP needs to be independent from the ISPs and that normally requires applying for a class-C subnet and an ASN from your national authority for this stuff. Then you can pretty much do what you need to, assuming you have an appropriate service from each ISPs. Of course, none of that comes cheap, and is hardly in the consumer or even SOHO category. I know that this stuff costs our company a small fortune, as everything in this service class is charged at extortion rates.
The alternative is to use a DNS failover service, although that is problematic for IPsec VPNs etc.