If your system has a complexity of X to build, and using a traditional RDBMS solves Y% up front, it adds an ongoing Z complexity overhead in growing/maintaining the system over time. NoSQL may have a lower Y, but it 's goal is to also have a lower Z, and can often win out in the bigger picture even without talking about massive scale. It's not true all the time, but in my experience it's been the general rule:)
In any sufficiently complex system a combination of both usually work well together. I heard a good offhand comment this week of "80% of the structure should be in an RDBMS and 80% of the data should be via NoSQL" which makes a lot of sense to me.
This thing is amazing, as long as the kids don't start watching youtube:)
half way and thoroughly enjoying it
on
Anathem
·
· Score: 1
I love the allusions, ties to earthly terminology, familiar yet alien setting, deep history and constant geeking out. It's a tremendous book so don't listen to the reviewer.
Imagine it as an alien story that someone actually translated/localized in every way possible, then consider what math and theory as a fundamental religion might do for long term stability.
We also already have one of these in the US, a decommissioned underground facility converted to an ultra-secure datacenter with green power, http://usshc.com/ who also hosts a number of open source projects like http://jabber.org/ and has stellar service and commodity rates.
Cascade IA has been doing this for a while now (small independent local telco), rings of fiber running throughout the sprawling metropolis (~2k population) and even out to within reach of all the rural customers.
For a while now all new homes even have fiber run to the premesis... difficult to believe we're "ahead of the times" back here in Iowa but it seems to be true:)
Agreed, I've been doing exactly this kind of thing for quite some time as well, as demonstrated at http://on2me.com/, by pushing data back through images.
I don't know about others, but I've had problems with xmlhttprequest and security settings for some IE users, it's not all it's cracked up to be.
Heh, these blights you speak of that Microsoft customers experience, perhaps the most logical answer here is that standard market forces will produce better competing OSes, such as OSX and (eventually) a good Linux Desktop.
I've been living on powerbooks for years now, I can't begin to tell you how peaceful and comfortable it is, that's powerful.
That's a very limited perspective, and I'll gamble that as we come to further understand how the universe works, we'll overcome such boxed mindsets.
Netscape Mosaic v 0.93 Beta/Scrnshots/Easter Eggs
on
Netscape Turns 10
·
· Score: 2, Interesting
http://jeremie.com/misc/moz/ is a page I put together some time ago that has a slightly newer rev of the original with some screenshots and as much as I could dig out of the executable as far as easter eggs, the about:authors is pretty cool IMO:)
Man, I spent so much time in awe in front of that thing, last time that happened was OSX... the net really needs something cool again.
Take a better look at Jabber
on
Enterprise IM?
·
· Score: 5, Insightful
It's not just open source, the XMPP protocol is approaching RFC status, and there is a whole suite of commercial products utilizing it.
Just take a gander at the Sponsors box on jabber.org for starters. You'll find products that drop into almost any environment, are based on open technologies, and can be complimented by many hundreds of open source apps... what could be better?
Closed IM systems are a thing of the past, if we want them to be.
No, Jabber doesn't have the VoIP industry support, they don't seem to be interested in streaming voice in XML, go figure.
But no, SIP doesn't have the open IM industry support, even MS's implementation is skewered, utilizes Windows Media APIs, and isn't even compliant in the end, go figure again.
The Jabber community is actually making a stand, changing things, finally influencing the big guys, a community-born open standard is moving forward and showing real signs of creating a truly unencumbered honest to god netural open platform for IM for everyone else.... tens of thousands of servers and millions of users *do* still make a difference in this DMCApressing big corporate brother digital world.
If you want a simple (heh) open solid supported IM standard, check out XMPP, seek not the SIP hammer for this job:)
Is this universe actually capable of creating true near-infinite randomness, or are all the sources fundamentally affected by characteristics relating to the beginning (and/or end) and basic properties underlying them?
Excellent, I hope you don't mind if I linked to it from the small developer meta-index on zeroconf/mdns site dotlocal.
This is all very old technology, but it's done in such a way that it's transparent, and that transparency in modern chaotic networks is more useful than ever, I for one am a fan of Rendezvous and even did a small ground-up implementation myself (mdnsd).
I know not of his endevours with patents/licenses, but I was quite impressed with his Manifesto on Atari's corporate identity.
The points about fairness, customers, and particularly on innovation are something I wish every modern CEO or company official would take to heart, but anymore there doesn't seem to be enough genuine spirit and ideals in american corps.
Yup, just started one a week or two ago, and just got it working today for the first time... still a long ways to go, but the code is designed to be super-simplistic C and embeddable into any OS app. You can check it out and the progress from my site or live view of the raw code.
I hope to have it start getting polished up in the next week, with some demo apps and utilities, make a project site for it, etc. Just jabber/email me at jer@jabber.org if your interested.
A couple choice quotes from the "whitepaper"
on
Cross-Site-TRACE
·
· Score: 5, Insightful
Typical Sky-Is-Falling (tm) propoganda, this is so 90's:
"Scenarios assume the following: A user visits a malicious web site or views malicious content hosted by a trusted source (message board, web mail, etc..)"
"To resolve this limitation, we had to utilize extended client-side scripting technologies to create and send a specially formatted HTTP request to a target web server." (this must pass through the web browser which must foolishly attach authentication cookies in question (which properly implemented secure systems don't rely on anyway))
"To restate, all the sensitive information is still accessible even over an SSL link." (what the hell? it's just the friggin headers! cookies and weak basic auth (they didn't even show and I'm not convinced the (broken) browsers send the auth headers in such forged requests)
"There is however at this point a limiting factor preventing wider a danger escalation. The TRACE connection made by the browser, will NOT be allowed by the browser, to connect to anything other than the domain hosting the actual script content... To increase the exposure of the exploit, we are in need of a domain-restriction-bypass vulnerability" (MAKE THIS CLEAR, IT ONLY WORKS IN A CROSS-SITE SCRIPTING VULNERABLE BROWSER)
To re-iterate: your web server or site isn't vulnerable because it supports trace, that's about as silly as blaming ping packets for the ping-of-death problems on early windoze systems, sheesh.
This is all a bunch of crap that requires a browser to be vulnerable to cross scripting, and for the user to have visited a malicious site just beforehand.
Re:My big problem with Jabber...
on
Programming Jabber
·
· Score: 4, Informative
What your talking about here is a particular implementation of a Jabber server, jabberd, not Jabber in general (people often confuse this point). You can do some minimal clustering with the jabberd-1.4 series, but probably not the kind of reliability that your looking for or that jabber.com has built into their server.
Jabber is an open system/protocol, anyone can build new servers/clients/etc with whatever features and extensions they want, including building it on/with xmlblaster. Jabberd is also an open source project that your welcome to help with (farming/clustering is a frequent need and I suspect that it will be a large part of the jabberd-1.5 development series).
Re:eXtensible Application Transport Protocol (XATP
on
HTTP's Days Numbered
·
· Score: 1
They're not quite doing the same thing, so it's hard to draw a direct comparison, but if you've read the BEEP specs it should be pretty easy to see the differences by reading the XATP draft. If anything, it might make more sense to look at a flavour of BEEP running over XATP.
If your interested in following this up in more detail, please feel free to join the spec-dev@xatp.org list.
Agreed!
If your system has a complexity of X to build, and using a traditional RDBMS solves Y% up front, it adds an ongoing Z complexity overhead in growing/maintaining the system over time. NoSQL may have a lower Y, but it 's goal is to also have a lower Z, and can often win out in the bigger picture even without talking about massive scale. It's not true all the time, but in my experience it's been the general rule :)
In any sufficiently complex system a combination of both usually work well together. I heard a good offhand comment this week of "80% of the structure should be in an RDBMS and 80% of the data should be via NoSQL" which makes a lot of sense to me.
The first artificial signal we've received via a medium we're only just discovering, perhaps? :)
This thing is amazing, as long as the kids don't start watching youtube :)
I love the allusions, ties to earthly terminology, familiar yet alien setting, deep history and constant geeking out. It's a tremendous book so don't listen to the reviewer. Imagine it as an alien story that someone actually translated/localized in every way possible, then consider what math and theory as a fundamental religion might do for long term stability.
We also already have one of these in the US, a decommissioned underground facility converted to an ultra-secure datacenter with green power, http://usshc.com/ who also hosts a number of open source projects like http://jabber.org/ and has stellar service and commodity rates.
I posted some of my own thoughts a few months ago comparing cloud computing to past patterns: A Wolf in Sheep's Clothing - the Return of the Mainframe as Cloud Computing
Everything repeats itself in some form :)
There's one hosting provider here in the US in a similar kind of ex-military facility: http://usshc.com/
They host the jabber.org project: http://www.xmpp.org/xsf/sponsors/
Finally! :)
There's some additional detail about the custom system they used in a PDF they published:
http://users.ox.ac.uk/~kgroup/publications/pdf/Rutz_crowcams_SOM.pdf
Cascade IA has been doing this for a while now (small independent local telco), rings of fiber running throughout the sprawling metropolis (~2k population) and even out to within reach of all the rural customers.
:)
For a while now all new homes even have fiber run to the premesis... difficult to believe we're "ahead of the times" back here in Iowa but it seems to be true
Agreed, I've been doing exactly this kind of thing for quite some time as well, as demonstrated at http://on2me.com/, by pushing data back through images.
I don't know about others, but I've had problems with xmlhttprequest and security settings for some IE users, it's not all it's cracked up to be.
Heh, these blights you speak of that Microsoft customers experience, perhaps the most logical answer here is that standard market forces will produce better competing OSes, such as OSX and (eventually) a good Linux Desktop.
I've been living on powerbooks for years now, I can't begin to tell you how peaceful and comfortable it is, that's powerful.
That's a very limited perspective, and I'll gamble that as we come to further understand how the universe works, we'll overcome such boxed mindsets.
http://jeremie.com/misc/moz/ is a page I put together some time ago that has a slightly newer rev of the original with some screenshots and as much as I could dig out of the executable as far as easter eggs, the about:authors is pretty cool IMO :)
Man, I spent so much time in awe in front of that thing, last time that happened was OSX... the net really needs something cool again.
Yeah, what's up w/ kids these days... yeesh
It's not just open source, the XMPP protocol is approaching RFC status, and there is a whole suite of commercial products utilizing it.
Just take a gander at the Sponsors box on jabber.org for starters. You'll find products that drop into almost any environment, are based on open technologies, and can be complimented by many hundreds of open source apps... what could be better?
Closed IM systems are a thing of the past, if we want them to be.
No, Jabber doesn't have the VoIP industry support, they don't seem to be interested in streaming voice in XML, go figure.
:)
But no, SIP doesn't have the open IM industry support, even MS's implementation is skewered, utilizes Windows Media APIs, and isn't even compliant in the end, go figure again.
The Jabber community is actually making a stand, changing things, finally influencing the big guys, a community-born open standard is moving forward and showing real signs of creating a truly unencumbered honest to god netural open platform for IM for everyone else.... tens of thousands of servers and millions of users *do* still make a difference in this DMCApressing big corporate brother digital world.
If you want a simple (heh) open solid supported IM standard, check out XMPP, seek not the SIP hammer for this job
Is this universe actually capable of creating true near-infinite randomness, or are all the sources fundamentally affected by characteristics relating to the beginning (and/or end) and basic properties underlying them?
Excellent, I hope you don't mind if I linked to it from the small developer meta-index on zeroconf/mdns site dotlocal.
This is all very old technology, but it's done in such a way that it's transparent, and that transparency in modern chaotic networks is more useful than ever, I for one am a fan of Rendezvous and even did a small ground-up implementation myself (mdnsd).
I know not of his endevours with patents/licenses, but I was quite impressed with his Manifesto on Atari's corporate identity.
The points about fairness, customers, and particularly on innovation are something I wish every modern CEO or company official would take to heart, but anymore there doesn't seem to be enough genuine spirit and ideals in american corps.
Yup, just started one a week or two ago, and just got it working today for the first time... still a long ways to go, but the code is designed to be super-simplistic C and embeddable into any OS app. You can check it out and the progress from my site or live view of the raw code.
I hope to have it start getting polished up in the next week, with some demo apps and utilities, make a project site for it, etc. Just jabber/email me at jer@jabber.org if your interested.
To re-iterate: your web server or site isn't vulnerable because it supports trace, that's about as silly as blaming ping packets for the ping-of-death problems on early windoze systems, sheesh.
This is all a bunch of crap that requires a browser to be vulnerable to cross scripting, and for the user to have visited a malicious site just beforehand.
The Jabber Software Foundation has set up a site to help coordinate and serve as a discussion area and repository for claims, including a patent lawyer's interpretation.
What your talking about here is a particular implementation of a Jabber server, jabberd, not Jabber in general (people often confuse this point). You can do some minimal clustering with the jabberd-1.4 series, but probably not the kind of reliability that your looking for or that jabber.com has built into their server.
Jabber is an open system/protocol, anyone can build new servers/clients/etc with whatever features and extensions they want, including building it on/with xmlblaster. Jabberd is also an open source project that your welcome to help with (farming/clustering is a frequent need and I suspect that it will be a large part of the jabberd-1.5 development series).
They're not quite doing the same thing, so it's hard to draw a direct comparison, but if you've read the BEEP specs it should be pretty easy to see the differences by reading the XATP draft. If anything, it might make more sense to look at a flavour of BEEP running over XATP.
If your interested in following this up in more detail, please feel free to join the spec-dev@xatp.org list.