오늘 제 블로그 메인의 구글 광고에 너무나도 낯익은 사이트가 보였습니다. 자바스크립트 라이브러리 최신정보가 가장 잘 정리되어 있다고 개인적으로 생각하고, 자주 방문하는 파이어준 님 블로그 광고가 실려 있었습니다.

아! 이제 개인 블로거분들도 광고를 하는구나 많이 놀랐습니다. 비용이 많이 들지 않는지 궁금하네요. 파이저준님은 왜 광고를 시작했을까요?


Google maps Partner Day가 12월10일 삼성동 Coex 인터콘티넨털호텔에서 오후 4시에 열렸다. 세미나 장소 입구의 한쪽에는 Google 지도에 어떤 정보가 검색되면 좋은지 참가자들에게 물어보는 이벤트를 하고 있었고, 다른 쪽에서는 구글맵 서비스 시연을 하고 있었다.



















구글에서 이씨플라자로 소포를 하나 보내왔다. 우리회사는 구글 애드워즈 광고를 하는 - 금액은 그리 크지 않음- 광고주여서 연말이 되면 구글이 선물을 보내준다. 작년에는 전자앨범을 받았었는데, 선물을 받았다는 자체에 너무 신났었던것 같다.


Dare Obasanjo has done a comparison of two new protocols for accessing database style data via HTTP. These protocols, based on REST, are the Google Base and Microsoft's Astoria.
The basic concept between the two protocols is the same. URLs are used in lieu of SQL to specify queries. Relationships and filters must be encoded as part of the URL and all requests are GETs.
The first difference pointed out by Dare is that Astoria uses a hierarchical format to represent relationships. For example, to specify that you wanted the orders for customer key 5 you would have something like "/Customers[5]/Orders". Google Base, on the other hand, uses a flat model where categories and predicates have to be used to ferret out relationships.
Both support filtering and sorting, but Google Base has a richer syntax and support for full-text queries across all categories. Google Base does get a bit carried away however, with support for inline If/Else constructs.
Astoria does have a really nice feature called expand. It allows the user to indicate they also want the children nodes for the data they requested. This eliminates the need to perform 1+N queries to get a collection of rows and the related child rows. The data comes back as inline XML under the appropriate node.
Google Base likewise has some features not found in Astoria. For example one can turn on spelling correction, which works in a manner similar to Google Search. You can also filter out repetitive information using the Crowd feature. In the article, Dare requested, "all restaurants stored within Google Base but show no more than 2 per cuisine type".
Dare Obasanjo concludes:
In comparing both approaches there is a lot to like and dislike. I like the "expand" feature in Astoria as well as the fact that I can retrieve XML results from multiple paths of the hierarchy. However there does seem to be a paucity of operators and functions for better filtering of results.
From the Google Base data API, I love the "crowd" feature and having a full library of functions for performing tests within predicates. Also some of the operators such as the ones for finding results near a certain location are quite impressive although unnecessary for the majority of RESTful protocols out there. That said, I do think they went overboard on some of the features such as having if...else blocks within the URIs. I suspect that some of that complexity wouldn't have been needed if they just had hierarchies instead of a flat namespace that requires complex filtering to get anything out of it.

|
622 407 | |
-30 days today : 77 |
댓글을 달아 주세요
최근에 애드워즈에서 광고를 무료로 할 수 있는 쿠폰을 뿌렸는데 그것을 통해서 광고주가 아마 많이 늘었을 것입니다.
2009/11/07 12:37http://search.daum.net/search?w=tot&nil_profile=g&nil_Search=btn&sw=tot&q=%BE%D6%B5%E5%BF%F6%C1%EE+%B9%AB%B7%E1%B1%A4%B0%ED
위 링크를 통해서 관련 정보 보실 수 있습니다.
그런 일이 있었군요. 좋은 정보 감사합니다.
2009/11/07 20:58