david, thanks for writing back. i wasn't around during the time when they designed this core part of App Engine's data models, but one obvious thing that stands out in my mind as a good reason is the validation of these special fields.
if you had automated checks of this data, you would, presumably need some string that represents a valid URI. other reasons include consistency to the gData interface as well as the equivalent data in XML or Atom formats. if you want to allow blanks, it may be better to just leave them as StringProperty. -- wesley - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - "Core Python Programming", Prentice Hall, (c)2007,2001 "Python Fundamentals", Prentice Hall, (c)2009 http://corepython.com wesley.j.chun :: wesc+...@google.com developer relations :: google app engine -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
