storage

How can data written to a file really be flushed/synced with the block device by Java. I tried this code with NIO: FileOutputStream s = new FileOutputStream(filename) Channel c = s.getChannel() while(xyz) c.write(buffer) c.force(true) s.getFD().sync() c.close() I supposed that c.force(true) togehter with s.getFD().sync() should be sufficient because the doc for force states Forces any updates to this channel's file to be written to the storage device that contains it. If this channel's file resides on a local storage device then when this method returns it is guaranteed that all changes made

I'm not sure how to use the XMPPFramework's core data to store incoming messages. Does anyone have any tutorials on how to do this? I see User objects, which in turn can have many "resources". Is each message received supposed to be a new resource that I create and persist? I do not know what part is my responsibility and what part the framework provides regarding message history. I can intercept every incoming message. Then am I supposed to create and store each message inside a Messages table using core data? I'd have a Message Entity. And each XMPPUser would have an array of Message objects

When a user uploads an image to my site, the image goes through this process; user uploads pic store pic metadata in db, giving the image a unique id async image processing (thumbnail creation, cropping, etc) all images are stored in the same uploads folder So far the site is pretty small, and there are only ~200,000 images in the uploads directory. I realise I'm nowhere near the physical limit of files within a directory, but this approach clearly won't scale, so I was wondering if anyone had any advice on upload / storage strategies for handling large volumes of image uploads. EDIT: Creating

What is the difference between CharField() and TextField() in Django? The documentation says that CharField() should be used for smaller strings and TextField() should be used for larger strings. Okay, but where is the line drawn between "small" and "large"? What's going on under the hood here that makes this the case? It's a difference between RDBMS's varchar (or similar) — those are usually specified with a maximum length, and might be more efficient in terms of performance or storage — and text (or similar) types — those are usually limited only by hardcoded implementation limits (not a DB

What storage system should I use , If i'm going to deploy a outlook plugin with VSTO ? Is it possible to use outlook's , which is for email ? UPDATE I thought about SQL Express , but I think I should use the same thing with what outlook uses , that would save troubles SliverNinja - MSFT There are numerous options for you to consider, below I've listed all the ones I've seen used in the past. For Outlook-managed storage you could look into using StorageItem which is a hidden item inside a given folder ( Inbox, etc. ). Using the StorageItem you can add custom user properties and file attachments

My specific situation Property management web site where users can upload photos and lease documents. For every apartment unit, there might be 4 photos, so there won't be an overwhelming number of photo in the system. For photos, there will be thumbnails of each. My question My #1 priority is performance. For the end user, I want to load pages and show the image as fast as possible. Should I store the images inside the database, or file system, or doesn't matter? Do I need to be caching anything? Thanks in advance! While there are exceptions to everything, the general case is that storing