I know of plenty of projects using SQLITE. For megabyte to tens of megabyte size database, SQLITE is GREAT. For hundreds of megabytes, it can still be good, but needs careful design and tuning. For 100s of megabytes, use a client/server DB
We use it to back our web based products. The concurrency isn't great but can handle dozens of users easily. We have DBs ranging to the gigabyte size. To date, in the past 4 years, there have been virtually no serious issues with SQLITE. Pros:
quality code, excellent free and paid support public domain code excellent SQL 92 compliancy, with the exception of GRANT/REVOKE, which aren't relevant on this kind of DB compiles on tons of platforms from embedded to Windows/Mac/Linux. Fast, especially for SELECTs ACID UTF8/UTF16 compatible Full Text search module available (caveat: I haven't tried it and don't know how good it is) Well documented Thread safe
Here are the caveats:
- As noted, it's not client/server. So it's concurrency is limited. Multi users apps should carefully consider their usage of SQLITE. You can work around this up to a point of course, but eventually you'll hit contention. - For 100MB+ databases, consider client/server also. - SQLITE can only use one index (single or compound) in the WHERE column. - INSERTS are slow unless you batch them. This is because you are opening, closing, and flushing each time. So if you do one INSERT at a time, you'll whine about the speed. The time to insert say 10 things one at a time, is in my experience about the time to insert 1000 rows when wrapped in a transaction - Both pro and con: a db is a single file. That makes it easy to deal with, but can be problematic in some cases, especially larger DBs
The point is you as your own program might have escaped or regexed items incorrectly and be open to this attack. Of course you don't blindly depend on some "magic" function. Duh! but you yourself are mortal too. And I doubt many people knew about fullwidth/halfwidh unicode transforms.
The fact that one of the articles linked to this says they did a successful SQL injection SHOWS there are issues.
BTW insulting people is not normally a useful technique
Yes you are. The point is that various unicode characers may be translated by your backend language into a "normal" character
so uFF07 (I think that was one example) will become in your strings. Unless you escape or trash all unicode stuff. Which has it's own issues:)
Ok, ok, that's a rational one, and i guess there are other examples. Now explain the RATIONAL reason for the fake jobbenet ramsey confession. Wanting some publicity at the cost of incarceration and/or execution isn't rational.
I really don't want to come off as a know-it-all. Certainly writing a screenplay is HARD WORK. I've never done it. But Ender's Game strikes me as quite cinematic and possible to do. Let's go through your issues
1. The characters age from 6yrs old to 12 yrs old. That's a HUGE swing. Them being children and developing are two important themes that need to remain.
Yes, this is a Big Problem. Particular the whole issue of actors at that age. They will probably have to move the age to 12-16. Unfortunate,cuz it dilutes it a bit. OTOH it avoids the risk of the Cute Factor, and reduces people protesting the film because it shows violent young uns.
2. How are they going to film the Battle Room scenes? It's a 3d fight, so there really isn't a good way of doing it. I think the best way would almost be a first person view directly from Ender, so the battle flows as he sees it, but this would lead to problems in the final battle.
No argument here; it's hard. They have to show these, but shift the emphasis to the interpersonal stuff BETWEEN batttles; that's more important anyway (though the battles are fun:)0
3. The Computer Game at the end (i can't remember it's name). That is going to be an extremely difficult thing to replicate, and build tension with. The build up of hopelessness at the very end will be crucial (more so than in the book) and will be hard to pull of with blips of light.
The Computer Game at the end? I think I'm confused. There are two computer games.
1. Is the psychological little play game with the giant et al. Dump it or revamp it; too much time spent on it for screen time.
2. The game at the end? Show the thing as described, edited. It'll come over fine.
4. Will they even cover Peter Wiggin? It will be hard to do that as well, especially his rise to power on the nets...
Yep another problem. Unfortunately, I think that is something that indeed would have to be drastically redone. It doesn't work as is in a 2 hour film. This will be an issue.
5. Naked.
Nonsense, this is a nice metaphor, but not needed. Come on!
Sorry, it seems to me that SIP came way after NAT was widely deployed.
So it was an omission/flaw in the specification NOT to take NAT into account. Period.
Are things much easier without relayers, etc to get past NAT - sure is. But in the Real World almost everyone is NATTED.
SIP will remain insignicant in VOIP and Messaging deployment until some one (I'm sure someonme has) hacks around the NAT issues. And it is a weakness of the RFC that it did not speciically state how to do so. IN so doing, they
a) marginalized SIP b) made messy kludges that weren't officially blessed and thus possibly not interoperable a way of life.
More importantly it needs a login server to assure unique ids, and bootstrap server nodes. Pretty easy to block really
http://arxiv.org/pdf/cs.NI/0412017
No one would. Name one major software company (MS included) that doesn't heavily use xml, soap, web serveices based on these things.
This is just a desperate money grab. No conspiracy here
If you want stsble long time, corporate quality distrib you buy Novell Linux Desktop or SLES/OES. Suse 10 is for hobbyists, and like the Suse Pro 9.x releases is a quarterly release cycle roughly.
Regardless of your statement you have to sell 100 pieces of MacOSx SOFT for every one copy of MacOSX "PC" for your #'s to make sense.
Of course absolute #'s matter. But if Apple sells 100 PC's a year (including MACOSX) for $1000 (deliberate underestimate!), they would make a lot more than 100 MacOSX software for $100. A lot more.
The ratio of potential sales matters.
Ok, will you pay $1000 for a MacOSX that will run on any PC?
Cuz that's what you seem to be asking for. Otherwise please explain how they will make money. Profits from selling OS's are only in the ten's of dollars. You will have to convince them they will SELL (eg not pirated) 100x more volume.
for his comments to be relevant (as with MS-linux comparisons BTW), you have to normalize to install base and time. Absolute #s have very little meaning
Eg, if I have one hacked system that year and only 1000 installed systems. That's 1 hack per 1000 systems per year. (1/1000 *1000]
If I have 1 million systems, and have 10 hacked systems, that's 10/1000000 *1000, that's.01 hacks per 1000 systems per year
What is to stop him?
Only the fact none of the movie rights for anything except the Hobbit and LOTR were sold, and the Tolkien Estate has been pretty unhappy about movies being made for any reason, saying they cheapen the book experience (I'm paraphrasing).
The snippets of pre-LOTR history such as the Last Alliance were only usable because they were directly discussed in LOTR. Similarly one could cobble together PIECES of the appendices, but they are largely insufficient for any additional full story with the possible exception of the Fall of the Kingdom of the North (there is enough outline there, though little flesh, to make a story, but I don't think it would be that successful).
But the Silmarillion core story material is offlimits.
at
http://www.viguard.com/en/news_view.php?num=88
which is viguard's side of the story. They quote a ZDNET story where Guilermito is a virus writer and then go step by step to reply to his accusations
But you have to take in account
a) training of OpenOffice
b) imperfect (pretty good, but imperfect) compatibility with MS office.
c) porting of things like VBA scripts, etc that don't work with OO (or hss this changed recently0
So the gap is probably more like 500,000 instead of a million. Or less.
Please try to think intelligently like a business must. Or else your comments are really not relevant, and do NOT HELP the cause of FOSS (dramatically the opposite in fact)
I think what he's saying is (as his next sentence implies) since Windows FORMS is mostly just a fancy wrapper around the Win32 controls, he doesn't feel much really gets exposed from an IP point of view.
Slashdot Mirror
I know of plenty of projects using SQLITE. For megabyte to tens of megabyte size database, SQLITE is GREAT. For hundreds of megabytes, it can still be good, but needs careful design and tuning. For 100s of megabytes, use a client/server DB
We use it to back our web based products. The concurrency isn't great but can handle dozens of users easily. We have DBs ranging to the gigabyte size. To date, in the past 4 years, there have been virtually no serious issues with SQLITE.
Pros:
quality code, excellent free and paid support
public domain code
excellent SQL 92 compliancy, with the exception of GRANT/REVOKE, which aren't relevant on this kind of DB
compiles on tons of platforms from embedded to Windows/Mac/Linux.
Fast, especially for SELECTs
ACID
UTF8/UTF16 compatible
Full Text search module available (caveat: I haven't tried it and don't know how good it is)
Well documented
Thread safe
Here are the caveats:
- As noted, it's not client/server. So it's concurrency is limited. Multi users apps should carefully consider their usage of SQLITE. You can work around this up to a point of course, but eventually you'll hit contention.
- For 100MB+ databases, consider client/server also.
- SQLITE can only use one index (single or compound) in the WHERE column.
- INSERTS are slow unless you batch them. This is because you are opening, closing, and flushing each time. So if you do one INSERT at a time, you'll whine about the speed. The time to insert say 10 things one at a time, is in my experience about the time to insert 1000 rows when wrapped in a transaction
- Both pro and con: a db is a single file. That makes it easy to deal with, but can be problematic in some cases, especially larger DBs
The point is you as your own program might have escaped or regexed items incorrectly and be open to this attack. Of course you don't blindly depend on some "magic" function. Duh! but you yourself are mortal too. And I doubt many people knew about fullwidth/halfwidh unicode transforms. The fact that one of the articles linked to this says they did a successful SQL injection SHOWS there are issues. BTW insulting people is not normally a useful technique
Yes you are. The point is that various unicode characers may be translated by your backend language into a "normal" character so uFF07 (I think that was one example) will become in your strings. Unless you escape or trash all unicode stuff. Which has it's own issues :)
Ok, ok, that's a rational one, and i guess there are other examples. Now explain the RATIONAL reason for the fake jobbenet ramsey confession. Wanting some publicity at the cost of incarceration and/or execution isn't rational.
I agree, but simply finding believable actors at that age is nearly impossible IMO
I really don't want to come off as a know-it-all. Certainly writing a screenplay is HARD WORK. I've never done it. But Ender's Game strikes me as quite cinematic and possible to do. Let's go through your issues 1. The characters age from 6yrs old to 12 yrs old. That's a HUGE swing. Them being children and developing are two important themes that need to remain. Yes, this is a Big Problem. Particular the whole issue of actors at that age. They will probably have to move the age to 12-16. Unfortunate,cuz it dilutes it a bit. OTOH it avoids the risk of the Cute Factor, and reduces people protesting the film because it shows violent young uns. 2. How are they going to film the Battle Room scenes? It's a 3d fight, so there really isn't a good way of doing it. I think the best way would almost be a first person view directly from Ender, so the battle flows as he sees it, but this would lead to problems in the final battle. No argument here; it's hard. They have to show these, but shift the emphasis to the interpersonal stuff BETWEEN batttles; that's more important anyway (though the battles are fun :)0
3. The Computer Game at the end (i can't remember it's name). That is going to be an extremely difficult thing to replicate, and build tension with. The build up of hopelessness at the very end will be crucial (more so than in the book) and will be hard to pull of with blips of light.
The Computer Game at the end? I think I'm confused. There are two computer games.
1. Is the psychological little play game with the giant et al. Dump it or revamp it; too much time spent on it for screen time.
2. The game at the end? Show the thing as described, edited. It'll come over fine.
4. Will they even cover Peter Wiggin? It will be hard to do that as well, especially his rise to power on the nets...
Yep another problem. Unfortunately, I think that is something that indeed would have to be drastically redone. It doesn't work as is in a 2 hour film. This will be an issue.
5. Naked.
Nonsense, this is a nice metaphor, but not needed. Come on!
at least to have an informeed comment :)
http://icann.org/announcements/announcement-21nov0 5.htm/
Sorry, it seems to me that SIP came way after NAT was widely deployed.
So it was an omission/flaw in the specification NOT to take NAT into account. Period.
Are things much easier without relayers, etc to get past NAT - sure is. But in the Real World almost everyone is NATTED.
SIP will remain insignicant in VOIP and Messaging deployment until some one (I'm sure someonme has) hacks around the NAT issues. And it is a weakness of the RFC that it did not speciically state how to do so. IN so doing, they
a) marginalized SIP
b) made messy kludges that weren't officially blessed and thus possibly not interoperable a way of life.
Bad job SIP committee!
More importantly it needs a login server to assure unique ids, and bootstrap server nodes. Pretty easy to block really http://arxiv.org/pdf/cs.NI/0412017
No one would. Name one major software company (MS included) that doesn't heavily use xml, soap, web serveices based on these things. This is just a desperate money grab. No conspiracy here
If you want stsble long time, corporate quality distrib you buy Novell Linux Desktop or SLES/OES. Suse 10 is for hobbyists, and like the Suse Pro 9.x releases is a quarterly release cycle roughly.
He's right. This is really straightforward and intuitively obviou. Nothing to learn here folks, move along
Regardless of your statement you have to sell 100 pieces of MacOSx SOFT for every one copy of MacOSX "PC" for your #'s to make sense. Of course absolute #'s matter. But if Apple sells 100 PC's a year (including MACOSX) for $1000 (deliberate underestimate!), they would make a lot more than 100 MacOSX software for $100. A lot more. The ratio of potential sales matters.
Ok, will you pay $1000 for a MacOSX that will run on any PC? Cuz that's what you seem to be asking for. Otherwise please explain how they will make money. Profits from selling OS's are only in the ten's of dollars. You will have to convince them they will SELL (eg not pirated) 100x more volume.
for his comments to be relevant (as with MS-linux comparisons BTW), you have to normalize to install base and time. Absolute #s have very little meaning Eg, if I have one hacked system that year and only 1000 installed systems. That's 1 hack per 1000 systems per year. (1/1000 *1000] If I have 1 million systems, and have 10 hacked systems, that's 10/1000000 *1000, that's .01 hacks per 1000 systems per year
deliberate, to test for correct parsing and fallback. those matter too you know
What is to stop him? Only the fact none of the movie rights for anything except the Hobbit and LOTR were sold, and the Tolkien Estate has been pretty unhappy about movies being made for any reason, saying they cheapen the book experience (I'm paraphrasing). The snippets of pre-LOTR history such as the Last Alliance were only usable because they were directly discussed in LOTR. Similarly one could cobble together PIECES of the appendices, but they are largely insufficient for any additional full story with the possible exception of the Fall of the Kingdom of the North (there is enough outline there, though little flesh, to make a story, but I don't think it would be that successful). But the Silmarillion core story material is offlimits.
at http://www.viguard.com/en/news_view.php?num=88 which is viguard's side of the story. They quote a ZDNET story where Guilermito is a virus writer and then go step by step to reply to his accusations
But you have to take in account a) training of OpenOffice b) imperfect (pretty good, but imperfect) compatibility with MS office. c) porting of things like VBA scripts, etc that don't work with OO (or hss this changed recently0 So the gap is probably more like 500,000 instead of a million. Or less. Please try to think intelligently like a business must. Or else your comments are really not relevant, and do NOT HELP the cause of FOSS (dramatically the opposite in fact)
I think what he's saying is (as his next sentence implies) since Windows FORMS is mostly just a fancy wrapper around the Win32 controls, he doesn't feel much really gets exposed from an IP point of view.