Ever heard of SuSE Open Exchange? It's a replacement for Microsoft Exchange Server and seems to work well. But from what I recall from a corporate standpoint if you use Outlook to connect to a non-Exchange Server client in this manner you *could* be possibly violating their EULA. Not sure on that last point 100% though.
No, you aren't a copyright infringer. But if you took the book, placed it facedown on a Xerox machine, copied a single page, and distributed to someone else you would be. P2K music sharing is a lot more quick and convenient. But sharing copyrighted works is still illegal.
I'm not saying the law itself is right or wrong. Justified or unjustified. But it is the law. Back when I was in high school I would copy cassette tapes that friends loaned me. I really wasn't afraid that the RIAA would be sending a summons. But nevertheless I broke the law.
The "War on Drugs" analogy isn't really applicable. P2P participants are the drug suppliers as well as the drug users. If you rip a new CD you just bought so others can download the files for their own use then you are a pusher that is a valid target, right?
This biased story line read like an excerpt from Les Miserables or Oliver Twist. If I don't like the 35 MPH speed limit on the road leading to my home I can't commute 70 MPH every day and not expect repercussions. If you don't like a law why not attack it legislatively? Make a grassroots effort to overturn the law. But don't knowingly break the law and expect to get any sympathy from me.
Hmmm. Tell that to the person who was just left off the published list. Coming in at #51 the much-underrated Russell Johnson. Better known as "The Professor" on Gilligan's Island. Tell me he wasn't a one person team for those guys.
So many people are griping about VZW on these threads. In my experience they have the best, most reliable coverage and the largest footprint. I know now that AT&T Wireless and Cingular have joined forces their network might be more encompassing. But CDMA coverage far surpasses GSM in terms of transmission strength and range. Look at T-Mobile as an example. Go inside any most buildings and try using their service. Drop city. GSM at its finest.
Sprint uses CDMA and has a decent footprint. But their towers aren't nearly as prevalent as those of VZW. My wife had a Sprint phone while I had a VZW handset and around the same areas day in and day out her calls would inevitably drop. I have full strength going all around our metro area (Columbus, OH).
After working as a tech for the wireless industry, and after having peers in other wireless companies I can tell you that VZW is hard to beat from the phone end of things. As for customer service, pricing and other matters that's a different story.
For wireless Internet data I have a T-Mobile PC Card with unlimited Internet access for $29 a month. Not bad. Of course the price is right and the signal strength isn't. It's always something:-(
Not to troll, but honestly. Isn't it perhaps just a rung on the ladder above IR transmission? I mean the range, security, etc. isn't anything to do handsprings about. The only people I typically hear ranting and raving about Bluetooth are PHB and other execs who like cashing in on buzzwords so they sound savvy.
I personally would hope for eventual adoption of the 802.11i standard so that wifi has added security. Once that happens why not add that feature onto phones? After all most of the dataflow PHB's and execs are trying to hook into involve public wifi hotspots, corporate WLAN's, etc. Bluetooth is more for standing 10 feet away or closer from another device and using a divining rod if that doesn't work.
Actually I can think of plenty of projects that haven't started out fragmented. Both open and closed source. Projects that aren't meant to be add-on fixes typically start out with some sort of focus. My reply was more of a tongue-in-cheek take and wasn't meant to be an IT directive. Geez, touchy, touchy...
Fragmented Justification
on
Hardening Apache
·
· Score: 3, Interesting
The creators of Apache Server came up with the name due to it being based on a series of patches for httpd. "A Patchy Server." Get it? The name itself suggests its fragmented beginnings.
Is that anything like...
on
Hardening Apache
·
· Score: 4, Funny
a cigar store wooden Indian? Sorry, I hadda say it...
I think this parent post makes a valid point. There are so many posts thrown around in many story comments that suggest reinventing the wheel just so that apps are written in the latest scripting language and using the latest IDE toolset. Sure you can improve things or migrate things. But totally scrap something and start all over again from scratch? That's a pretty desparate measure. If I was the boss I certainly would want a detailed explanation supporting why someone would need to tank so much of their time.
Our company has Great Plains for its accounting and G/L package. When Micro$oft bought out Great Plains we saw the coming trend and purchased SQL Server 2000 since eventually they would retire Novell and Pervasive as supported platforms. Since we already had the SQL Server in place it seemed like the quickest way to go when we were upsizing the Access-based app. Emphasis on "quick."
Years ago I had used MySQL in a couple of projects. For lookups (i.e. - a bunch of SELECT statements) it seemed to shine. Our transactions involve a lot of record-level locks and heavy inserts/updates. Recently MySQL with the InnoDB addon seems to be worthy of consideration. But I think I might wait awhile to see how things continue on in this area.
I have been in the same boat many a time. I remember one time some brainchild tried rolling out an Access app across three sites spread out across the country. He kept on saying, "It seems fast to me. What are you guys complaining about??" Not realizing he was looking at the LAN end of the app. The rest of us were many a hop away.
Then this genius figured that if the WAN response time for these huge chunks of data was too slow perhaps he could force some Access database replication scheme. Nice try.
And the people who put these projects together sometime fail to grasp the difference between OLE DB, ODBC, native SQL, etc. connection methods. They think because ODBC is so easy it must be the best, fastest connection method. Right!
I would place Access in the same realm as some small homegrown app that relies on an MSDE back-end. Take it beyond a handful of concurrent users and you're out of your realm.
Access if an effective rapid application development tool, but really doesn't scale well if the application grows beyond the original scope. I can give you many examples from my previous jobs, but here's the most recent one.
Our company created a homegrown Access-based database for tracking repair jobs. Eventually once we planned to expand operations to multiple site locations (connected via WAN) we knew that Access would be dog-slow and would need to be scrapped.
So we tried taking the first step of migrating by moving the database itself to SQL Server 2000 and porting the front end from Access into Visual Basic.
The problem is that the underlying VB methods were still rooted in the poor Access conventionalities. Pulling huge ADO Recordsets across for simple table inserts is a perfect example. SQL Server has views and stored procedures which weren't being leveraged. Bringing over all of the Access GUI methods left us with a clumsy interface at best.
If you are talking about just using Access for its drag and drop GUI elements perhaps it's a good **start.** But sooner or later someone will need to get into the barebones of the code if an application is going to scale effectively. The conventionalities Access relies on are frankly not very impressive. The time it takes to tweak everything makes a good argument for starting out in another programming language from the get-go.
Most places I've worked we've taken the corporate attitude that if someone wants to create their own Access application it has to be local to their site (i.e. - no WAN reliance) and IT wasn't responsible to maintenance and support.
I recall years ago working for the RAID manufacturing division of Conner (the hard drive/tape drive company, which was bought out by Seagate). The building right down the street from ours was responsible for tech support of their tape drives and backup software.
What did our facility use for backup software? Not Backup Exec! We used Legato Networker. I recall some tours the corporate big wigs were given every now and then. Their expressions were funny to see if they peeked in the server room!
Probably not, since they are talking about the stem cells extracted from living adults, not aborted or lab-grown embryos. There is a difference. Bush's administration has funded non-embryonic stem cell research for awhile now.
If you take some old codger with oesteoporosis, grow them some new bones, and then add in a mechanical exoseleton and I think we're all in a world of hurt. Bingo night will look something akin to a Terminator installment.
Same with phishing attempts. I view the e-mail's document source to find the redirected site. Then contacting the site's listed web hosting company and domain name hosting company usually helps keep things in check. Not to mention contacting the supposed company being misrepresented (PayPal, eBay, U.S. Bank, etc.) with those same contact details.
1) Do absolutely nothing. 2) If anything happens tomorrow pull the plug on the DSL router we use for Internet access. 3) Plug the router back in after a few hours. 4) Repeat step 1.
Good point. That and the fact that there is a newly discovered 'Drag and Drop' exploit in XP SP2 where using an Internet Explorer's scroll bar is enough to drop a binary executable in your Windows Startup folder. Perhaps there's more underground exploits that meets the eye. I just gathered details about the 'Drag and Drop' deal from Secunia.
Not at my company's firewall, although SANS shows a big spike in port hits across their polling community. I just blocked this port at our firewall now in case...
Not to be argumentative regarding this, but is e-mail the best method to blindly send a proof? Most companies (even with storage being pennies per pound) have limits to file attachment size. And from experience I know grpahics files are huge.
The times I have had to deal with such measures involved using FTP or burning a CD to be sent next day AM. And if I was dealing with a transfer of a last minute, under deadline document I would certainly follow up blindly sending it to someone with a phone call to ensure they received it. People do that with everything from faxes to shipped packages FFS!
Slashdot Mirror
Ever heard of SuSE Open Exchange? It's a replacement for Microsoft Exchange Server and seems to work well. But from what I recall from a corporate standpoint if you use Outlook to connect to a non-Exchange Server client in this manner you *could* be possibly violating their EULA. Not sure on that last point 100% though.
No, you aren't a copyright infringer. But if you took the book, placed it facedown on a Xerox machine, copied a single page, and distributed to someone else you would be. P2K music sharing is a lot more quick and convenient. But sharing copyrighted works is still illegal. I'm not saying the law itself is right or wrong. Justified or unjustified. But it is the law. Back when I was in high school I would copy cassette tapes that friends loaned me. I really wasn't afraid that the RIAA would be sending a summons. But nevertheless I broke the law.
The "War on Drugs" analogy isn't really applicable. P2P participants are the drug suppliers as well as the drug users. If you rip a new CD you just bought so others can download the files for their own use then you are a pusher that is a valid target, right?
This biased story line read like an excerpt from Les Miserables or Oliver Twist. If I don't like the 35 MPH speed limit on the road leading to my home I can't commute 70 MPH every day and not expect repercussions. If you don't like a law why not attack it legislatively? Make a grassroots effort to overturn the law. But don't knowingly break the law and expect to get any sympathy from me.
Now, now. Let's not "jump to conclusions"...
Hmmm. Tell that to the person who was just left off the published list. Coming in at #51 the much-underrated Russell Johnson. Better known as "The Professor" on Gilligan's Island. Tell me he wasn't a one person team for those guys.
I'm game! Greg_Kujawa@yahoo.com
So many people are griping about VZW on these threads. In my experience they have the best, most reliable coverage and the largest footprint. I know now that AT&T Wireless and Cingular have joined forces their network might be more encompassing. But CDMA coverage far surpasses GSM in terms of transmission strength and range. Look at T-Mobile as an example. Go inside any most buildings and try using their service. Drop city. GSM at its finest.
:-(
Sprint uses CDMA and has a decent footprint. But their towers aren't nearly as prevalent as those of VZW. My wife had a Sprint phone while I had a VZW handset and around the same areas day in and day out her calls would inevitably drop. I have full strength going all around our metro area (Columbus, OH).
After working as a tech for the wireless industry, and after having peers in other wireless companies I can tell you that VZW is hard to beat from the phone end of things. As for customer service, pricing and other matters that's a different story.
For wireless Internet data I have a T-Mobile PC Card with unlimited Internet access for $29 a month. Not bad. Of course the price is right and the signal strength isn't. It's always something
Not to troll, but honestly. Isn't it perhaps just a rung on the ladder above IR transmission? I mean the range, security, etc. isn't anything to do handsprings about. The only people I typically hear ranting and raving about Bluetooth are PHB and other execs who like cashing in on buzzwords so they sound savvy.
I personally would hope for eventual adoption of the 802.11i standard so that wifi has added security. Once that happens why not add that feature onto phones? After all most of the dataflow PHB's and execs are trying to hook into involve public wifi hotspots, corporate WLAN's, etc. Bluetooth is more for standing 10 feet away or closer from another device and using a divining rod if that doesn't work.
Actually I can think of plenty of projects that haven't started out fragmented. Both open and closed source. Projects that aren't meant to be add-on fixes typically start out with some sort of focus. My reply was more of a tongue-in-cheek take and wasn't meant to be an IT directive. Geez, touchy, touchy...
The creators of Apache Server came up with the name due to it being based on a series of patches for httpd. "A Patchy Server." Get it? The name itself suggests its fragmented beginnings.
a cigar store wooden Indian? Sorry, I hadda say it...
I think this parent post makes a valid point. There are so many posts thrown around in many story comments that suggest reinventing the wheel just so that apps are written in the latest scripting language and using the latest IDE toolset. Sure you can improve things or migrate things. But totally scrap something and start all over again from scratch? That's a pretty desparate measure. If I was the boss I certainly would want a detailed explanation supporting why someone would need to tank so much of their time.
Our company has Great Plains for its accounting and G/L package. When Micro$oft bought out Great Plains we saw the coming trend and purchased SQL Server 2000 since eventually they would retire Novell and Pervasive as supported platforms. Since we already had the SQL Server in place it seemed like the quickest way to go when we were upsizing the Access-based app. Emphasis on "quick."
Years ago I had used MySQL in a couple of projects. For lookups (i.e. - a bunch of SELECT statements) it seemed to shine. Our transactions involve a lot of record-level locks and heavy inserts/updates. Recently MySQL with the InnoDB addon seems to be worthy of consideration. But I think I might wait awhile to see how things continue on in this area.
I have been in the same boat many a time. I remember one time some brainchild tried rolling out an Access app across three sites spread out across the country. He kept on saying, "It seems fast to me. What are you guys complaining about??" Not realizing he was looking at the LAN end of the app. The rest of us were many a hop away.
Then this genius figured that if the WAN response time for these huge chunks of data was too slow perhaps he could force some Access database replication scheme. Nice try.
And the people who put these projects together sometime fail to grasp the difference between OLE DB, ODBC, native SQL, etc. connection methods. They think because ODBC is so easy it must be the best, fastest connection method. Right!
I would place Access in the same realm as some small homegrown app that relies on an MSDE back-end. Take it beyond a handful of concurrent users and you're out of your realm.
Access if an effective rapid application development tool, but really doesn't scale well if the application grows beyond the original scope. I can give you many examples from my previous jobs, but here's the most recent one.
Our company created a homegrown Access-based database for tracking repair jobs. Eventually once we planned to expand operations to multiple site locations (connected via WAN) we knew that Access would be dog-slow and would need to be scrapped.
So we tried taking the first step of migrating by moving the database itself to SQL Server 2000 and porting the front end from Access into Visual Basic.
The problem is that the underlying VB methods were still rooted in the poor Access conventionalities. Pulling huge ADO Recordsets across for simple table inserts is a perfect example. SQL Server has views and stored procedures which weren't being leveraged. Bringing over all of the Access GUI methods left us with a clumsy interface at best.
If you are talking about just using Access for its drag and drop GUI elements perhaps it's a good **start.** But sooner or later someone will need to get into the barebones of the code if an application is going to scale effectively. The conventionalities Access relies on are frankly not very impressive. The time it takes to tweak everything makes a good argument for starting out in another programming language from the get-go.
Most places I've worked we've taken the corporate attitude that if someone wants to create their own Access application it has to be local to their site (i.e. - no WAN reliance) and IT wasn't responsible to maintenance and support.
I recall years ago working for the RAID manufacturing division of Conner (the hard drive/tape drive company, which was bought out by Seagate). The building right down the street from ours was responsible for tech support of their tape drives and backup software. What did our facility use for backup software? Not Backup Exec! We used Legato Networker. I recall some tours the corporate big wigs were given every now and then. Their expressions were funny to see if they peeked in the server room!
Probably not, since they are talking about the stem cells extracted from living adults, not aborted or lab-grown embryos. There is a difference. Bush's administration has funded non-embryonic stem cell research for awhile now.
If you take some old codger with oesteoporosis, grow them some new bones, and then add in a mechanical exoseleton and I think we're all in a world of hurt. Bingo night will look something akin to a Terminator installment.
Same with phishing attempts. I view the e-mail's document source to find the redirected site. Then contacting the site's listed web hosting company and domain name hosting company usually helps keep things in check. Not to mention contacting the supposed company being misrepresented (PayPal, eBay, U.S. Bank, etc.) with those same contact details.
My strategy will consist of a different approach:
1) Do absolutely nothing.
2) If anything happens tomorrow pull the plug on the DSL router we use for Internet access.
3) Plug the router back in after a few hours.
4) Repeat step 1.
Don't rag on the WWN. I for one love reading up on Osama hanging out at strip joints and "Batboy's" latest escapades...
Good point. That and the fact that there is a newly discovered 'Drag and Drop' exploit in XP SP2 where using an Internet Explorer's scroll bar is enough to drop a binary executable in your Windows Startup folder. Perhaps there's more underground exploits that meets the eye. I just gathered details about the 'Drag and Drop' deal from Secunia.
Not at my company's firewall, although SANS shows a big spike in port hits across their polling community. I just blocked this port at our firewall now in case...
Not to be argumentative regarding this, but is e-mail the best method to blindly send a proof? Most companies (even with storage being pennies per pound) have limits to file attachment size. And from experience I know grpahics files are huge. The times I have had to deal with such measures involved using FTP or burning a CD to be sent next day AM. And if I was dealing with a transfer of a last minute, under deadline document I would certainly follow up blindly sending it to someone with a phone call to ensure they received it. People do that with everything from faxes to shipped packages FFS!