Do Office 2007 (docx, xlsx,...) and OpenOffice files are concerned about virus ? I've never seen many reports about virus inside these docs.
Anyway, I'don't think GA should worry about virus and IMO a link is less secure than an attachment. A virus in a link is scan once and generally an attachment is scanned twice (one by the antivir OS and the other by the mail server). Regards. Sylvain On 27 oct, 02:01, "Jason (Google)" <apija...@google.com> wrote: > This past Wednesday, the App Engine team hosted the latest session of > its bimonthly IRC office hours. A transcript of the session and a > summary of the topics covered is provided below. The next session will > take place on Wednesday, November 4th from 7:00-8:00 p.m. PST in the > #appengine channel on irc.freenode.net. > > Note that this will be the first Chat Time to occur after daylight > time in the U.S. ends, which means that it will be taking place one > hour earlier than usual in countries or states that don't observe > daylight savings time. Please be aware of this time difference so you > don't inadvertently miss the session. > > - Jason > > --SUMMARY----------------------------------------------------------- > - Q: Why am I seeing > 0.1% rate of datastore operations time out and > is anything being done to reduce this? A: A certain level of datastore > timeouts is expected (generally between 0.1% and 0.2% of all datastore > operations) but, we are actively working on ways to improve datastore > reliability. If you are seeing a much higher rate, be sure to inspect > your data model for write contention which often manifests as > datastore timeouts. [9:02-9:07] > > - Q: What is the recommended approach to datastore capacity planning > ahead of a large bulk upload? A: Entities are stored as protocol > buffers (http://code.google.com/p/protobuf/) -- if you familiarize > yourself with the protobuf specification, you can determine the space > needed to store each entity, minus the datastore overhead, fairly > easily. An article is coming out soon which explains how entities and > indexes are stored in much more detail. [9:04-9:05] > > - Q: Can a high level of read operations result in datastore > contention? A: Datastore contention is usually the result of too many > attempted concurrent writes to the same datastore entity or entity > group. Before implementing your data model, consider the expected read/ > write access patterns and design your data model accordingly, sharding > entities that you expect to update more than once per second (http:// > code.google.com/appengine/articles/scaling/contention.html). While > concurrent writes generally result in contention, concurrent reads > generally result in better performance due to caching. [9:08-9:09, > 9:11-9:13, 9:18] > > - Q: Are there any plans to support more file extensions for > attachments to outgoing email, e.g. .doc, .docx, etc.? A: There are no > immediate plans to support these extensions due to the prevalence of > viruses contained in files of these types. In the meantime, you can > include links to the files or share them via Google Docs. [9:14, 9:16, > 9:19-9:20] > > - Q: What is the recommended approach to paging large data sets in App > Engine? A: The offset approach is *not* recommended because it won't > work for result sets larger than 1,000. Until datastore cursors are > available, the recommended approaches are summarized > inhttp://code.google.com/appengine/articles/paging.html. [9:21-9:23] > > - Q: How can one avoid exploding indexes when using list properties? > A: In general, you should avoid referencing more than one list > property in any query, especially if one or both list properties > contain a large number of elements. Index rows have to be added for > every permutation of values in the lists, which can result in index > "explosion". See the video > athttp://sites.google.com/site/io/under-the-covers-of-the-google-app-en... > to learn more about why exploding indexes occur. [9:22, 9:26, > 9:28-9:30, 9:32-9:33, 9:40] > > - Q: In Java, can one use sequence methods in JPA to get a sequence of > datastore IDs? A: No, you have to use the low-level datastore API's > allocateIds() method for now. [9:31, 9:33] > > - If you're looking to use Google Web Toolkit (GWT) and App Engine > together, there are a number of combo samples available > inhttp://code.google.com/p/googleappengine/source/browse/#svn/trunk/jav... > including gwtguestbook, sticky, and taskengine. [9:46, 9:48, > 9:50-9:51] > > - Q: What is being done to address long initialization times for Java > applications? A: We are definitely aware of the issue and are rolling > out several back-end enhancements over the next few releases to try to > minimize this startup time as much as possible. [9:52-9:53] > > --FULL TRANSCRIPT--------------------------------------------------- > [09:01am] scudder_google: Hi all, welcome to another instlallment of > our hour long chat time with people on the App Engine team > [09:01am] johnvdenley: Is there any kind of formality to this session? > or is it just a free for all? > [09:01am] moraes: take what you can! > [09:02am] moraes: meh. > [09:02am] Jason_Google_: johnvdenley: It's basically a free-for-all. > [09:02am] scudder_google: so far from Google we have nickjohnson, > Jason_Google and a few others may join as we go > [09:02am] scudder_google: yes, jump right in questions and comments > welcome > [09:02am] mbw: Is anything being done to reduce timeouts? I am seeing > a lot more than .01% timeouts. We even use a low level catch and > retry trick to try and reduce its effect. We saw a huge spike of them > yesterday at one point. > [09:02am] johnvdenley: OK, brb then, just need to move my car!... > [09:03am] scudder_google: mbw are these timeouts with datastore > operations? > [09:03am] mbw: yes > [09:03am] nickjohnson: mbw: We're actively working on datastore > timeouts. Bear in mind that they frequently highly correlated: When > you see them at all, they come in batches. > [09:04am] brett_ae: heyo > [09:04am] dw: re: idle question from last week, is there any good > advice going on capacity planning for datastore? i note that even very > small entities have a metadata overhead of 100+ bytes, and was > wondering how that metadata number is calculated (is it constant, > dependent on indexed fields, field count, etc.) > [09:04am] scudder_google: ah ok, there are a few things that you can > do but a small percentage of timeouts is currecntly expected > [09:04am] mbw: we see a steady amount of timeouts during the day. > [09:04am] mbw: i'd be happy with .01% ... > [09:05am] Jason_Google_: dw: I have an article coming out really soon > that explains all this. I'll try to get it published in the next week, > if you can hold out. > [09:05am] nickjohnson: dw: Entities are stored as Protocol Buffers; > the overhead in the datastore stats is simply the total size of the > entity's PB less the space used for each field. > [09:05am] dw: Jason_Google: that's great. more a curiosity than > anything right now > [09:05am] scudder_google: I'm assuming these are timeouts on writes, > about how many indexes need to be updated with a write > [09:05am] nickjohnson: The simplest way to reduce overhead is to use > shorter field names. > [09:05am] dw: nice > [09:06am] mbw: timeouts happen on reads for us as much as writes. > They don't seem to happen any more on big operations vs. small simple > queries or gets > [09:06am] nickjohnson: You can specify the field name to use > internally to the Property subclass constructor, by the way, so you > don't need to compromise the design of your model. > [09:06am] dw: nickjohnson: +10 points for preempting the evil thoughts > i was having > [09:07am] nickjohnson: mbw: Do you typically tend to write a lot to > the same entity groups? > [09:07am] scudder_google: mbw: ah ok, I'd like to look into this more > sepecifically for your app, what is the app ID? > [09:07am] mbw: scudder_google: ill PM it > [09:07am] moraes: i was thinking alongthe lines of 'store everything > in a big pickle property named "a".' > [09:08am] _tmatsuo: Talking of timeouts, if there's too many accesses > to a particlar node in a short period of time, could it be a reason > for datastore timeouts? > [09:08am] nickjohnson: moraes: Pickle is, amongst other things, > bulky. > [09:09am] nickjohnson: _tmatsuo: For a given value of 'too many', yes > [09:09am] brett_ae: _tmatsuo: for writes, possibly; for reads, no; it > should actually get faster > [09:09am] brett_ae: because of caching > [09:09am] johnvdenley: whats the status of a local datastore viewer? > [09:09am] moraes: johnvdenley: there's one. > [09:10am] dw: johnvdenley: /_ah/admin/datastore url when running > dev_appserver > [09:11am] Jason_Google_: johnvdenley: A local data viewer was added in > the Java SDK a couple of releases back. > [09:11am] mbw: scudder_google: did you receive my PM? > [09:11am] _tmatsuo: nick: brett_ae: thanks. In such a case(timeouts on > writes because of massive access), in my opinion, re-partitioning of > data will help reducing timeouts. Is there any mechanism for re- > partitioning of data? > [09:12am] scudder_google: mbw: yes, just replied, apologies for the > delay > [09:12am] nickjohnson: _tmatsuo: That's too general a question to > answer as-is. It depends highly on the data model in question. > [09:12am] nickjohnson: Frequently, simple optimisations do make a big > difference, though > [09:12am] brett_ae: _tmatsuo: you can do a migration (by changing your > schema/entity groups) yourself, which can be difficult; easiest thing > to do is think about your datamodel ahead of time and think of your > read/write access patterns > [09:12am] johnvdenley: ah, apologies, i must have been reading an old > message > [09:13am] brett_ae: _tmatsuo: So if you know you're writing to a > single piece of data more than once per second, maybe split it > somehow? > [09:14am] max-oizo: When I was doing "diff" between versions 1.2.5 and > 1.2.6, I found a CompiledQuery. What is it? Part future support > cursors? > [09:14am] Sylvain_: News to support new extensions in the e-mail > service ? and particularly MS Office (Word, Excel) and Open Office > files ? (issue 494). > [09:14am] brett_ae: max: > [09:14am] Sylvain_: For example, We'd like to create a "HR section" > where people can send their resum (most of the time) : .doc, docx. > We'd like to send them by mail then. > [09:14am] Sylvain_: And if possible not case sensitive (issue 493) > [09:16am] brett_ae: sylvain_: It's something we should support; the > concern thus far ... > > plus de détails » --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
