Tilted Forum Project Discussion Community - View Single Post

Robaggio · 03-30-2005, 02:20 PM

Here's the project:

1) Users pay via credit card online to join a group.
2) Users login to the system which provides a content specific webpage in regards to their group.

This is about as basic as I can make things. It's not a huge endeavor- nothing needs to be logged or monitored. All data is harmless and low-priority (save the credit cards info, which is a one time thing) so we're not worried about making things very grand. I'm most concerned about my limitations in the future as far as delivering the data.

The current design for the project is oriented around filtering information from the database. Currently there are no plans to do any computations or processing on-the-fly of the information. However, the goal is to develop the project with the assumption that such tasks will be created.

My incling for this project is to do it in PHP. It's fast, easy, and works so smoothly with MySQL. It will also mesh well with the current design of the website which uses CSS for a modular approach. The question however, is what to do down the line? I realize that ASP.NET is merely a platform- if we chose to use it, we'd develop in C# and/or Java. This would allow much more conceptual flexability becuase of better object oriented design. It's not to say that PHP can't do these things. Rather, that if things were to become very complex, it would be easier to plan them out with a higher-level language.

In the long run, I see both approaches fairly equal. PHP will be quicker to start- It'll be easy to talk to the database in long or short run. However, it'll be more difficult to conceptually plan out more complex tasks. With ASP.NET there will be a slower start, but conceptual design will be easy. Talking to the database will be more difficult however, as ASP.NET is not as seemless as PHP. I don't mind either just so long as things don't switch once the project has started.

I suppose that given the scope of the project, things will ultimately boil down to opinions. I'm curious as to what you folks think. Also, if there are any suggestions, I'm all ears.

03-30-2005, 02:20 PM	#1 (permalink)
Robaggio Crazy	PHP vs. ASP.NET Here's the project: 1) Users pay via credit card online to join a group. 2) Users login to the system which provides a content specific webpage in regards to their group. This is about as basic as I can make things. It's not a huge endeavor- nothing needs to be logged or monitored. All data is harmless and low-priority (save the credit cards info, which is a one time thing) so we're not worried about making things very grand. I'm most concerned about my limitations in the future as far as delivering the data. The current design for the project is oriented around filtering information from the database. Currently there are no plans to do any computations or processing on-the-fly of the information. However, the goal is to develop the project with the assumption that such tasks will be created. My incling for this project is to do it in PHP. It's fast, easy, and works so smoothly with MySQL. It will also mesh well with the current design of the website which uses CSS for a modular approach. The question however, is what to do down the line? I realize that ASP.NET is merely a platform- if we chose to use it, we'd develop in C# and/or Java. This would allow much more conceptual flexability becuase of better object oriented design. It's not to say that PHP can't do these things. Rather, that if things were to become very complex, it would be easier to plan them out with a higher-level language. In the long run, I see both approaches fairly equal. PHP will be quicker to start- It'll be easy to talk to the database in long or short run. However, it'll be more difficult to conceptually plan out more complex tasks. With ASP.NET there will be a slower start, but conceptual design will be easy. Talking to the database will be more difficult however, as ASP.NET is not as seemless as PHP. I don't mind either just so long as things don't switch once the project has started. I suppose that given the scope of the project, things will ultimately boil down to opinions. I'm curious as to what you folks think. Also, if there are any suggestions, I'm all ears. Last edited by Robaggio; 03-30-2005 at 02:31 PM..