Funny you should say that. The company I work for has a number of SCO servers, and we are now looking to replace them with Linux boxes because of all this nonsense. (We already have a number of new servers running Linux - it's the legacy ones that are still running SCO).
SCO's 'support' costs an arm and a leg, and is pretty lousy. They do not fix problems in a timely manner, and many software packages that run on their OS are usually old and obsolete.
Canada does this. And it works. Perhaps takes a bit longer to report the results, because they all have to be counted by hand, but the system works well. It's also not confusing. No punch outs, no complicated UIs to learn. Simply put a checkmark in the circle next to the candidate's name. Just to make sure, they put an example of what the checked box should look like, right on the top of the ballot.
All ballots are put in a securely-sealed box, which is opened up in front of officials representing the parties and counted.
Simple premise - everyone in the world signs onto the 'KarmaMail' service, and get to send mail at "1". Once enough KarmaMail users validate the user's email as being legitimate, their Karma goes up. Registered users can also complain about a spammer, thus making their Karma go down. Marking email messages as 'urgent' requires a higher Karma. Users with a negative Karma (>= -5?) can only send at '0'. Users with a very negative Karma get booted off the system.
Then individual users can use Karma plus Whitelists to decide who to read mail from. Whenever a server receives mail, it checks with the central KarmaMail repository and inserts the user's Karma into the mail headers (optionally, Karma can be assigned to the *server* as well, eliminating the open relay problem). The header can then be processed by the mail reader.
Maybe someone would care to expand this idea further to clear up the many loopholes I've left?
I got tired of buying the car charger every time I got a new phone. My solution? Get a cheap inverter (I got a 75W one from Canadian Tire) and keep it in your car. Then just use your regular charger with it.
So it'll take them that long just to sue the Americans who are using P2P. Guess I've got about two thousand years before they set their sights on Canada, eh?
Err, nevermind. I don't care for American music anyway.
I'm leading a team of developers using Velocity for a large e-Business application, with many modules. It's a beauty to use, and our solution has won a few awards last year. We use a custom framework (not Struts, not VelocityServlet) to choose templates to load, since our app is designed to be highly customizable for each of our customers (medium or large business, including government). We also keep the locale in the session, and load the appropriate localized Velocity template if available. Let's just say this app is quite large. We now have well over a thousand Velocity templates, built up over the last few years.
Unfortunately I'm not at liberty to identify the application or the company here, because the company is actually very much a Microsoft shop, and it's been a major political issue that I've had our team move our application away from Microsoft solutions (it used to be VB/ASP). But it's performed well and never let us down (although the 1.3 release of Velocity was quite buggy and we had to revert to 1.2 until 1.3.1 came out).
I would wholeheartedly recommend Velocity. I had our team start using it because we ran into a huge mess with ASP (which I knew would repeat with JSP). Enforcing code separation between your view and your model is important, and Velocity does it beautifully. It avoids having a lot of unnecessary (and unmaintainable) cruft mixed in with your HTML.
If you need more specific information, we can discuss it by email. I'll be happy to help you in any way that I can.
I remeber the outrage that by taking out one telephone exchange you could sever the east and west coasts of Australia during the olypics. And IIRC taking out another 4 centres would disconnect Australia from the world.
It's already happened to us. In Canada, a fire in a Bell exchange (in Toronto) cut off the telephones for most of the eastern portion of the whole country. It was about 4 years ago, IIRC, and everyone had to use cell phones for a while. Except then, the cell networks got overloaded too:)
Was a messy couple of days. They got it back up pretty quickly, though. But it was pretty annoying for the consulting company I worked for - we had to use email for all of our communication with our customers.
I submit the old t-shirt design. The editors won't notice.
Even the bloody shirts will be DUPES! Dammit, man, that'd be just a little too real for me.
What we need is a Beowulf cluster in Soviet Russia figuring out why the secret to life, the universe and everything seems to have something to do with Natalie Portman petrified, and hot grits. 42 of 'em, I guess.
The only time a (key, object) pair in a session gets replicated is if Session.set...() has been called for that pair during this request/response cycle.
Hmm...
This seems impractical. You either lose your abstraction by having to make the session available to any part of the app which might change your object's state, or you lose efficiency by just having to assume that it's changed and force a 'set' every time it *might* have changed.
Perhaps the Java Servlet API needs to include another interface. Something along the lines of 'StateChangeNotifier' (which of course extends Serializable).
The Session.set() will accept only a StateChangeNotifier object (not just any Object). Basically, this interface defines a way for the session to register itself with that object, so that the session can know when that object's state has changed using some sort of event mechanism.
Obviously the person who implements that object would need to make sure that the event is thrown whenever something changes. But then again... what if that object contains other objects whose state might change? Arrrrgggh.
I guess you just have to force the replication if there's any chance it might have changed. Crap. This is a serious problem and an invitation for bugs with less-experienced developers, IMO.
For example, objects in Sessions must be Serializable when clustering.
I have a question about that I've been wondering about for a while. How does the session know to replicate an object that's changing? For example, if during a request/response a mutator method is called on that object?
Say, for example, I have a Vector stored in the session. And each time a request is processed, something is added or removed from that Vector. If you never actually call set...() on the Session (just get the vector, then set something within it), does this actually get replicated correctly?
I'm a bit curious as to how that would work internally.
One of the things that Al Gore did that was really nice was give dirt cheap rates (sometimes free depending on the school and their demographics) on T1 lines for schools and educational institutions.
It's great that the inventor himself was able to maintain his hold on how his product is used. Good for him!
Slashdot Mirror
Both of them?
Funny you should say that. The company I work for has a number of SCO servers, and we are now looking to replace them with Linux boxes because of all this nonsense. (We already have a number of new servers running Linux - it's the legacy ones that are still running SCO).
SCO's 'support' costs an arm and a leg, and is pretty lousy. They do not fix problems in a timely manner, and many software packages that run on their OS are usually old and obsolete.
Ever try running Java code on SCO?
Canada does this. And it works. Perhaps takes a bit longer to report the results, because they all have to be counted by hand, but the system works well. It's also not confusing. No punch outs, no complicated UIs to learn. Simply put a checkmark in the circle next to the candidate's name. Just to make sure, they put an example of what the checked box should look like, right on the top of the ballot.
All ballots are put in a securely-sealed box, which is opened up in front of officials representing the parties and counted.
Funny you ask. SSO has a unique design in which the wings fold during re-entry
Anyone else read that as SCO the first time? I almost jumped out of my chair... what? You mean they've got their grubby fingers in this IP pie too?
If they know that this kernel has their so-called trade secrets in there, why the hell are they still distributing it on their own FTP site?
Doesn't the fact that they're still distributing the kernel under the GPL, even after all this lawsuit nonsense, nullify all of their claims?
Heh.
Still trying to figure out how to get 'net access to my cottage. How much would it cost to get a wireless signal to travel about 200km?
They'll be taking questions! Somebody call them up and ask them about the stock dumping!
Think about what you're saying! Do you want a girlfriend that:
never has time for you
too into the game to bathe for weeks at a time
more interested in game than sex
kicks your ass in Quake
I didn't think so
Can't we use Karma?
Simple premise - everyone in the world signs onto the 'KarmaMail' service, and get to send mail at "1". Once enough KarmaMail users validate the user's email as being legitimate, their Karma goes up. Registered users can also complain about a spammer, thus making their Karma go down. Marking email messages as 'urgent' requires a higher Karma. Users with a negative Karma (>= -5?) can only send at '0'. Users with a very negative Karma get booted off the system.
Then individual users can use Karma plus Whitelists to decide who to read mail from. Whenever a server receives mail, it checks with the central KarmaMail repository and inserts the user's Karma into the mail headers (optionally, Karma can be assigned to the *server* as well, eliminating the open relay problem). The header can then be processed by the mail reader.
Maybe someone would care to expand this idea further to clear up the many loopholes I've left?
I got tired of buying the car charger every time I got a new phone. My solution? Get a cheap inverter (I got a 75W one from Canadian Tire) and keep it in your car. Then just use your regular charger with it.
So it'll take them that long just to sue the Americans who are using P2P. Guess I've got about two thousand years before they set their sights on Canada, eh?
Err, nevermind. I don't care for American music anyway.
How's about one of the old-style fax machines?
email me:
arozeluk [at thingy] websoup [period] net
Anyone else notice the QOTD on the bottom of this page right now? Draw your own conclusions...
'There's small choice in rotten apples. -- William Shakespeare, "The Taming of the Shrew"'
Absolutely!
I'm leading a team of developers using Velocity for a large e-Business application, with many modules. It's a beauty to use, and our solution has won a few awards last year. We use a custom framework (not Struts, not VelocityServlet) to choose templates to load, since our app is designed to be highly customizable for each of our customers (medium or large business, including government). We also keep the locale in the session, and load the appropriate localized Velocity template if available. Let's just say this app is quite large. We now have well over a thousand Velocity templates, built up over the last few years.
Unfortunately I'm not at liberty to identify the application or the company here, because the company is actually very much a Microsoft shop, and it's been a major political issue that I've had our team move our application away from Microsoft solutions (it used to be VB/ASP). But it's performed well and never let us down (although the 1.3 release of Velocity was quite buggy and we had to revert to 1.2 until 1.3.1 came out).
I would wholeheartedly recommend Velocity. I had our team start using it because we ran into a huge mess with ASP (which I knew would repeat with JSP). Enforcing code separation between your view and your model is important, and Velocity does it beautifully. It avoids having a lot of unnecessary (and unmaintainable) cruft mixed in with your HTML.
If you need more specific information, we can discuss it by email. I'll be happy to help you in any way that I can.
Bad news for Tivo?
No. I think it's bad GNUs for Tivo.
I remeber the outrage that by taking out one telephone exchange you could sever the east and west coasts of Australia during the olypics. And IIRC taking out another 4 centres would disconnect Australia from the world.
:)
It's already happened to us. In Canada, a fire in a Bell exchange (in Toronto) cut off the telephones for most of the eastern portion of the whole country. It was about 4 years ago, IIRC, and everyone had to use cell phones for a while. Except then, the cell networks got overloaded too
Was a messy couple of days. They got it back up pretty quickly, though. But it was pretty annoying for the consulting company I worked for - we had to use email for all of our communication with our customers.
feed the source to his dog, and get a job with the NSA?
The last thing the world needs is an AIBO that learns about our vulnerabilities. Isn't this how the whole Terminator mess got started?
Shit, man! You've just copied 15 lines of SCO code from their kernel! They're gonna sue your ass!
http://ssshotaru.homestead.com/files/aolertranslat or.html
Taco, is that you in there?
I submit the old t-shirt design. The editors won't notice.
Even the bloody shirts will be DUPES! Dammit, man, that'd be just a little too real for me.
What we need is a Beowulf cluster in Soviet Russia figuring out why the secret to life, the universe and everything seems to have something to do with Natalie Portman petrified, and hot grits. 42 of 'em, I guess.
This CNN article has a photo.
Last I checked, ads don't count.
Pick it up and find out that you just ordered and paid for, a battleship anchor, express delivery to your house.
So you're the prick who outbid me on e-Bay!
The only time a (key, object) pair in a session gets replicated is if Session.set...() has been called for that pair during this request/response cycle.
Hmm...
This seems impractical. You either lose your abstraction by having to make the session available to any part of the app which might change your object's state, or you lose efficiency by just having to assume that it's changed and force a 'set' every time it *might* have changed.
Perhaps the Java Servlet API needs to include another interface. Something along the lines of 'StateChangeNotifier' (which of course extends Serializable).
The Session.set() will accept only a StateChangeNotifier object (not just any Object). Basically, this interface defines a way for the session to register itself with that object, so that the session can know when that object's state has changed using some sort of event mechanism.
Obviously the person who implements that object would need to make sure that the event is thrown whenever something changes. But then again... what if that object contains other objects whose state might change? Arrrrgggh.
I guess you just have to force the replication if there's any chance it might have changed. Crap. This is a serious problem and an invitation for bugs with less-experienced developers, IMO.
For example, objects in Sessions must be Serializable when clustering.
I have a question about that I've been wondering about for a while. How does the session know to replicate an object that's changing? For example, if during a request/response a mutator method is called on that object?
Say, for example, I have a Vector stored in the session. And each time a request is processed, something is added or removed from that Vector. If you never actually call set...() on the Session (just get the vector, then set something within it), does this actually get replicated correctly?
I'm a bit curious as to how that would work internally.
One of the things that Al Gore did that was really nice was give dirt cheap rates (sometimes free depending on the school and their demographics) on T1 lines for schools and educational institutions.
It's great that the inventor himself was able to maintain his hold on how his product is used. Good for him!