Featured post

c# - Usage of Server Side Controls in MVC Frame work -

i using asp.net 4.0 , mvc 2.0 web application. project requiremrnt have use server side control in application not possibl in noraml case. ideally want use adrotator control , datalist control. i saw few samples , references in codepleax mvc controllib howwver found less useful. can tell how utilize theese controls in asp.net application along mvc. note: please provide functionalities related adrotator , datalist controls not equivalent functionalities thanks in advace. mvc pages not use normal .net solution makes use of normal .net components impossible. a normal .net page use event driven solution call different methods service side mvc use actions , view completly different way handle things. also, mvc not use viewstate normal .net controlls require. found article discussing mixing of normal .net , mvc.

python - Storing Templates and Object-Oriented vs Relational Databases -


i'm designing custom blog software, , have run conundrum regarding database design. software requires there multiple content types, each of require different entry forms , presentation templates.

my initial instinct create these content types objects, serialize them , store them in database json or yaml, entry forms , templates simple strings attached "contenttypes" table. seems cumbersome, however. there established best practices dealing design? use case should consider object database?

if should using object database, should consider? working in python , prefer capable python library, can move java if need be.

please not store templates (that might altered user) in database. there's no sane way migrate staging environment production if have deal doffs of database dumps. dumping software right 1 reason.

apart i'd store source (user editable part) in database plus "precompiled version" either directly in database (for faster retrieval) or in cache system.

i'd go set theory approach.

  • store each set of content type precompiled , recompile when edited fast serving in separate place (table, collection, directory, whatever)
  • store sources in common place make easy rebuild different content types (the source format special case content type)
  • keep templates in place migration between systems (dev, staging, prod) makes migration easy

Comments

Popular posts from this blog

c# - Usage of Server Side Controls in MVC Frame work -

cocoa - Nesting arrays into NSDictionary object (Objective-C) -

ios - Very simple iPhone App crashes on UILabel settext -