Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I have a calendar (ie a set of events) that I would like to make publicly available with a technique that allows from as many platforms (windows,ios,android,...) as possible to subscribe/import to this calendar.
I've been reading for a while on solutions for sharing calendars online and I am a bit puzzled:
sometimes you are told that all you need to do is to make an ics file online available; that seems logical to me, but that would mean that anyone adding this link in their calendar software always downloads the entire (large) ics file with all the events?
sometimes I read about CalDav which seemed to me more like an alternative to the blunt download strategy of ics. If I understood well, software able to handle CalDav links can sync in an intelligent way with a calendar server (but is there a lot of end-user software available to handle CalDav links?)
I found very little on the efficiency of making calendars available online, as well from the user point of view (not nice if you need to download the entire ics file on every read) as from the server point of view. Any help or insight in available techniques would be great.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
This question is a little more generic, a brainstorm one. I'm about to develop a small website, and I still don't know if it’s better for me to store my “Text” (to fill Labels, Messages, etc) data on the Database or just on the frontend.
I know that for a fact, consulting the BackEnd Database is slower than just searching a specific file, but it’s also better to update the list later-on (when the website is developed) by just running a script.
I want to know some opinions, experiences, advantages and disadvantages about both.
Edit: For the technologies, i was thinking in using ExtJS with a Java Backend, I'm not quite sure about the BD yet.
Consider what data you are storing and the purpose of your website.
Advantages of front end storage: quicker
Advantages of database storage: more secure/structured
If your strings are sensitive then I would secure them in your database. Any client information, including "Text" data should be stored on the back end. If the strings are only relevant to you as the site owner then I don't see a problem with storing them on the front end.
Also perhaps specify which technologies you are using to build this site to get more specific responses.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
We've made this monitoring tool at our company.
It's not in our line of business so we might as well opensource the tool, and maybe someone else likes it as well, maybe they'll contribute.
The tool runs on AppEngine, so there are so the are some paths in the appengine configuration, that might be a good idea to keep hidden. Unless someone else wants to start using our appengine qouta.
Is there a best practice for open-sourcing AppEngine applications?
Does anyone have any experience to share regarding opensourcing appengine sites?
You can get some ideas from excellent gae-init. The way its working in order to avoid exposing sensitive information, is moving it in a stand alone project, you can even use gae-init for that ;)
As part of the model is a Config class which holds all the information as it concerns the service and its dependencies. There are some default values there but it can also be easily customized from a web interface called admin. Have a look.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
We know that Silverlight currently in 3.0.x version - very fast transition from Silverlight 2.0.x. For those using Windows and Mac, it will not be an issue since the runtime supports those platform. The problem is with Linux users. I know that Mono guys (through Moonlight project) are doing their best to keep it up to date with Silverlight, but unfortunately they are too much behind.
How do you offer Silverlight to clients considering that facts?
If your client base has "full support for Linux on the desktop" as a pre-req, you're really in an interesting niche -- one I'd love to learn more about, btw, but not one I've ever encountered. If you're REALLY in such a situation, I guess your only viable silverlight strategy is to limit your silverlight use to not much more than is currently available via moonlight, clearly document to your Linux-rabid clients what's missing on Moonlight for them to be able to use your latest release, and endeavor (via clients involvement, involvement of your tech people, bounties for developers that add each missing features, etc) to get Moonlight up to the level you absolutely need it to be!-)
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I've just finished a mini-project (a graphical 2d silverlight tag cloud) and I've made the source code available on my website as a zip file - but where should I put the code to allow people to find it and evolve it if they wish? codeplex? but I guess this would count as an inactive project?
http://sourceforge.net/
Find and Build
Open Source Software
Google Code is great, free, and easy. It supports subversion.
http://www.codeplex.com/ This is run by Microsoft, which should be a fine match with Silverlight.
I recommend github.
CodeProject is good too.
It depends upon what you plan to do.
If you want to share the code with the world and open it to large cooperation, definitely go github
If you want to setup a nice web site, with a complete community with mailing lists, and a selected number of authorized contributors, go sourceforge.
Alternatively, you could use one of the sourceforge-like : google code, codeplex, savannah, berlios...
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I'm working on a web application that is globalized. The development process is agile style, with several sprints already completed. Our globalization framework is good and localization efforts have been successful so far. However, we continue to run into questions during requirements development, particularly in data storage and validation requirements. I'm certain the questions we are wrestling with have been researched and solved many times and the answers are likely well known and documented somewhere. So far, I have been unable to find the compendium of information I'm looking for.
Here are some sample questions I'd like to find answers for:
What are the best practices for input, validation, storage and display of address information for a global application?
number of characters to store for address fields (Did you know there is a city name that contains 163 characters?)
validation of address data
What are the best practices for input, validation, storage and display of phone numbers for a global application?
Same question for a person's name?
So far, our approach to these issues has been to allow ample storage for the various fields and to perform minimal input validation, relying on the user to get it right. This approach is working OK at this stage in the project, but the various project stakeholders are not satisfied using this approach for the long term. There is a strong desire for clean data, efficient storage and attractive data presentation for all locales.
Any recommendations out there for books, papers or websites that have a fairly complete handling of these and related topics?
Lots of good information here.