The Active Network
ActiveMac Anonymous | Create a User | Reviews | News | Forums | Advertise  
 

  *  

  MSN 8 Asks Users to Pay for Some Online Services
Time: 16:00 EST/21:00 GMT | News Source: Gartner | Posted By: Byron Hinson

Microsoft's decision to move MSN to a partial for-pay model reasonably extends the trend in which content and application providers seek financial legitimacy by countering the popular mid-1990s assertion that information ("content" is the more common term in 2002) "wants to be free." The precipitous decline in competition among Internet information and interaction hubs makes the for-pay business model more defensible than ever — the critical issue here.

Write Comment
Return to News

  Displaying 451 through 475 of 1501
Prev | First | Last | Next
  The time now is 3:34:18 PM ET.
Any comment problems? E-mail us
#451 By 2459 (24.233.39.98) at 10/11/2002 2:06:13 AM
About that rock thing: I think Peter was Petros and the rock was Petra.

#452 By 1845 (12.254.162.111) at 10/11/2002 2:07:22 AM
I love the way he just said that Sun isn't near the threat that it once was.

#453 By 2459 (24.233.39.98) at 10/11/2002 2:07:24 AM
Yeah software politics can be pretty bad too, but it's a lot more fun to talk about.

#454 By 2459 (24.233.39.98) at 10/11/2002 2:08:02 AM
any dig at Sun is a good dig :-)

#455 By 1845 (12.254.162.111) at 10/11/2002 2:09:34 AM
"Can we count on you coming back to discuss the cone of silence next year?"

#456 By 1845 (12.254.162.111) at 10/11/2002 2:10:21 AM
thanks for the gartner link, i've been laughing for almost 15 solid mintues. this is really funny stuff.

#457 By 2459 (24.233.39.98) at 10/11/2002 2:11:08 AM
Are you gonna watch McNealy's interview?
I am. It should be funny. :-)

And have predictable digs at MS and IBM. If I could bet "the farm" on McNealy mentioning MS or IBM, I'd be richer than Sensei Bill Gates.

#458 By 2459 (24.233.39.98) at 10/11/2002 2:21:12 AM
I just noticed that the McNealy interview says "Replay will not be available". I guess Scott isn't too comfortable about the public seeing his responses. :-)

#459 By 1845 (12.254.162.111) at 10/11/2002 2:26:38 AM
I don't remember RMD (assuming it was him)'s comment about the Petros/Petra/Peter/rock thing. I wrote in that thread, what that scripture means to me. It seems to me that Jesus was talking about revelation or the relationship of a person with God. This relationship, it seems only natural, must be the basis of any church. If a person, and especially the leader of the church isn't communicating with God, the church is on a rather shaky foundation.

As far as Peter being head of the Church in his day, that is the way that I've always understood it. It seems that Peter, James, and John were the three that were the presiding group within the group of the twelve apostles. That's the way I see it.

As for religion being a sticky subject, you are so right! When I said to mhfm that I understood the difficulties being a missionary, I was being quite serious. Religion in specific, or the search for truth in genearl (some would say these are the same thing, some will say they are opposites) evokes very powerful emotions. If you feel you have found the truth, generally speaking you are going to share it with those that it will benefit who mean something to you. Since most religions (Christianity at least) deal with learning to love everybody, the drive when you become a Christian is to share that love that you feel from God with everybody else. The problem arises when your feelings conflict with others. It's very important material, but must be approached very carefully so as not to offend. Above all, I think, a religious fellow has to respect that other may or may not believe as he does.

#460 By 1845 (12.254.162.111) at 10/11/2002 2:29:32 AM
I had planned to watch the McNeally interview, but alas, it isn't available.

#461 By 1845 (12.254.162.111) at 10/11/2002 2:33:37 AM
what does SAN mean? i don't remember.

#462 By 1845 (12.254.162.111) at 10/11/2002 2:36:34 AM
acronymfinder.com is down. ahhh! i hate not knowing what an acronym means.

#463 By 1845 (12.254.162.111) at 10/11/2002 2:38:30 AM
storage area network (thanks, google). um, what is a storage area network?

#464 By 2459 (24.233.39.98) at 10/11/2002 2:47:39 AM
I believe it is comprised of those devices that are basically a harddrive with a NIC. Unless it means unified shared storage.

#465 By 1845 (12.254.162.111) at 10/11/2002 2:49:37 AM
what is unified shared storage?

#466 By 2459 (24.233.39.98) at 10/11/2002 2:58:19 AM
Hey Bob, when you are coding, say even a simple WinForms app, do you still try to make assemblies that you interface with, or do you just use the forms builder and add the needed code (assuming the majority or all of the code is readily available in the framework)? What methodology do you use for building software? How do you know where to start, and what to consider a feature that should be self contained?

I know this is a bit much, but I just wanted to get some info from someone in the industry on how to go about putting together software from the start so that it is coherent, maintainable, and flexible. I have an idea from looking at how MS' stuff works, but the main thing is how to start. Is there anything involved that speeds up or clarifies the process other than making a diagram, drilling down and rearranging until there is an obvious hierarchy, and writing sudocode, etc.?

#467 By 2459 (24.233.39.98) at 10/11/2002 2:59:57 AM
I was thinking along the lines of Server, dumb terminal, etc. where everything is stored on the server or accross a series of servers or networked disks.

#468 By 2459 (24.233.39.98) at 10/11/2002 3:25:18 AM
A storage area network (SAN) is a high-speed special-purpose network (or subnetwork) that interconnects different kinds of data storage devices with associated data servers on behalf of a larger network of users. Typically, a storage area network is part of the overall network of computing resources for an enterprise. A storage area network is usually clustered in close proximity to other computing resources such as IBM S/390 mainframes but may also extend to remote locations for backup and archival storage, using wide area network carrier technologies such as asynchronous transfer mode or Synchronous Optical Networks.
A storage area network can use existing communication technology such as IBM's optical fiber ESCON or it may use the newer Fibre Channel technology. Some SAN system integrators liken it to the common storage bus (flow of data) in a personal computer that is shared by different kinds of storage devices such as a hard disk or a CD-ROM player.

SANs support disk mirroring, backup and restore, archival and retrieval of archived data, data migration from one storage device to another, and the sharing of data among different servers in a network. SANs can incorporate subnetworks with network-attached storage (NAS) systems.

http://searchstorage.techtarget.com/sDefinition/0,,sid5_gci212937,00.html

MS supports this in Win2000 as well as another tech called system area network.

#469 By 2459 (24.233.39.98) at 10/11/2002 6:58:25 AM
New .NET Show available.
The Developer Roadmap
http://msdn.microsoft.com/theshow

#470 By 1845 (12.254.162.111) at 10/11/2002 12:57:04 PM
Sorry, I wasn't avoiding you. AT&T decided, hey, you must be taking too much advantage of the service for which you are paying. I think it is time for a network outage in your area.

Grr! There is nothing like surfing along then suddenly getting 404's until you realize you've lost your connection.

#471 By 1845 (12.254.162.111) at 10/11/2002 1:00:55 PM
Thanks for the SAN info. All this talk of a storage industry makes much more sense now.

#472 By 1845 (12.254.162.111) at 10/11/2002 1:34:23 PM
I'm writing this little intro after I wrote the message. Let me know if this answers your questions.

Application Design - Whether WinForms or WebForms or old school VB6 or ASP, I design the same way. I'm a hard core follower of the n-Tier architecture, so as far as it makes sense in any given project I'll have logic call code divisions for data access, business logic, and user interface. Because of the logic division, I doesn't really matter what your front end is, since the backend is independent of it.

That said, I roughly follow the principles in MSF (Microsoft Solution Frameworks) for Application Development. First you ask a lot of questions to find out the requirements of the app. You also need to find out logistical concerns (I want to access this part from my iPaq, we have very taxed line between our app server and our db, etc.).

From here you can do top down (UI to database) or bottom up (database to UI). I usually do bottom up. I'll create a new SQL Server db and start laying out tables. When designing the db, you can usually see if you forgot to ask any questions about the app or if anything needs clarifying.

The database design is followed by writing the CRUD (Create, Read, Update, Delete) layer. This layer has two parts. The first part (from a bottom up perspective) is the set of store procedures and functions in your db for manipulating your data. The second part is the code (C# in my case) that will call the stored procs. When writing procs, you only need to write the procs that will be called (of course). If, for instance, some data is not deletable, then you don't write procs to handle the "D" part of CRUD. In this manner, you enforce a portion of your business rules in code (or by the lack of code).

The next part is basically writing a C# wrapper for the stored procs. From an n-Tier perspective, you may want these to be all static, so that you don't have as little state as possible associated with your data access objects. Usually I'll have data access object in my data layer per real world object. Sometimes it makes more sense to let some wrapper object aggregate things for you.

For instance, in the case of a user, I'd have a user object. If I were writing a golf app (and I just did) I might not have a data object for a single golf club. I'd probably have one for the golf bag and let the golf bag object handle all manipulation for the clubs it contains. Either way would work (the bag object calling club objects which call clup stored procs or the bag object calling the club procs itself). It depends entirely on the situation how much separation or cohesion you need in your objects.

#473 By 1845 (12.254.162.111) at 10/11/2002 1:34:37 PM
Upon finishing fleshing out all the classes in your data layer, you move to business logic. This layer is extrememly important and most often (especially from those who are used to doing client server apps) gets lumped either in the datalayer or the UI. This layer doesn't need to be separate, but quite often it will save you time in modifying the app, if you have loosely coupled layers. Business logic does two things. It is basically the police man for the UI. It makes sure that if the UI requests data that it should receive that it doesn't receive that data. It makes sure that the UI gets data formatted in a way that makes sense to a specific client (this sometimes is handled by the UI itself, depends on your design). What I mean by formatted, is some clients might want an XML string (like web pages wanting to do XSL/T) and some might want little collections (like WinForms for binding to a combo box) and some might want fully populated datasets for use in many places. Business is also responsible for making sure the data offered to the data layer is clean. (This is often handled in UI too.) It should check to make sure all user input is sterile before giving it to the data layer. Sterile means that the data is valid (a password is of the correct length) and that it isn't malicious (that the password isn't really a SQL string trying to get itself executed in your db). Your business objects are also stateless.

Now that we have a custom app framework (specific for that app you are writing), you can attach any UI that suits you to it. I just wrote a desktop golf app in WinForms. I copied the business and data layers into an ASP.NET project and am coding against the exact same code in developing an online version of that app. This is one wonderful thing about being loosely coupled. Also, though, the more business logic you put in UI (UI is also called the presentation layer) the more you'll have to duplicate it when you use diffferent UI's - WinForms, WebForms, Mobile WebForms, etc.

#474 By 2459 (24.233.39.98) at 10/11/2002 6:56:31 PM
Thanks for the info, Bob.

No problem about the connection issues. I just figured you were busy. It allowed me to get some needed sleep. :-)

I hope you didn't suffer for too long (broadband withdrawl) :-)

#475 By 1845 (12.254.162.111) at 10/11/2002 7:43:54 PM
Once I was convinced my cable modem wasn't going to block sync for a while, I went to sleep myself.

Did I answer your questions about app design? I didn't get into when I'd use separate assemblies and stuff. I only talked about logical code division, not physical. To answer that question, I'd have to ask about the deployment environment and code technology. My answers for a COM based solution differ from my .NET answers.

Write Comment
Return to News
  Displaying 451 through 475 of 1501
Prev | First | Last | Next
  The time now is 3:34:18 PM ET.
Any comment problems? E-mail us
User name and password:

 

  *  
  *   *