473,322 Members | 1,287 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,322 software developers and data experts.

Article Storage: Files vs. Database

I'd like to build a Website that contains many articles. Two basic
approaches are to either store the articles in aspx files, possibly indexed
by the database, or to store the article text in the database.

Some advantages of storing them in files are simplicity, and efficiency.

Some advantages of storing them in the database are ease of some operations,
and the option of using SQL Server 2005 text index to implement search.

Can anyone else offer some considerations for choosing between these two
approaches?

Thanks.

Jonathan

Jun 27 '08 #1
13 1361
We use databases almost exclusively for this kind of "stuff". Its easier to
search, index, etc. and the content can be populated into a "templatized"
article page. It can also be cached via Partial page caching.
Peter

"Jonathan Wood" <jw***@softcircuits.comwrote in message
news:%2****************@TK2MSFTNGP02.phx.gbl...
I'd like to build a Website that contains many articles. Two basic
approaches are to either store the articles in aspx files, possibly
indexed by the database, or to store the article text in the database.

Some advantages of storing them in files are simplicity, and efficiency.

Some advantages of storing them in the database are ease of some
operations, and the option of using SQL Server 2005 text index to
implement search.

Can anyone else offer some considerations for choosing between these two
approaches?

Thanks.

Jonathan
Jun 27 '08 #2
Yeah, these are definitely some of the advantages. Have you made use of SQL
Server 2005's full-text indexing yet? With file-based articles, implementing
search is a pain.

Also, would love to see some samples of the sites you are referring to if
any of them are public.

Jonathan

"Peter Bromberg [C# MVP]" <pb*******@nospammin.yahoo.comwrote in message
news:83**********************************@microsof t.com...
We use databases almost exclusively for this kind of "stuff". Its easier
to search, index, etc. and the content can be populated into a
"templatized" article page. It can also be cached via Partial page
caching.
Peter

"Jonathan Wood" <jw***@softcircuits.comwrote in message
news:%2****************@TK2MSFTNGP02.phx.gbl...
>I'd like to build a Website that contains many articles. Two basic
approaches are to either store the articles in aspx files, possibly
indexed by the database, or to store the article text in the database.

Some advantages of storing them in files are simplicity, and efficiency.

Some advantages of storing them in the database are ease of some
operations, and the option of using SQL Server 2005 text index to
implement search.

Can anyone else offer some considerations for choosing between these two
approaches?

Thanks.

Jonathan
Jun 27 '08 #3
Implementing search functionality is pain.You might do it yourself or get
some third party solution like dtSearch or open source (just google "serarch
engine open source")

But from my experience the SQL server's full-text do not do a good job.

George.
"Jonathan Wood" <jw***@softcircuits.comwrote in message
news:eL****************@TK2MSFTNGP05.phx.gbl...
Yeah, these are definitely some of the advantages. Have you made use of
SQL Server 2005's full-text indexing yet? With file-based articles,
implementing search is a pain.

Also, would love to see some samples of the sites you are referring to if
any of them are public.

Jonathan

"Peter Bromberg [C# MVP]" <pb*******@nospammin.yahoo.comwrote in message
news:83**********************************@microsof t.com...
>We use databases almost exclusively for this kind of "stuff". Its easier
to search, index, etc. and the content can be populated into a
"templatized" article page. It can also be cached via Partial page
caching.
Peter

"Jonathan Wood" <jw***@softcircuits.comwrote in message
news:%2****************@TK2MSFTNGP02.phx.gbl...
>>I'd like to build a Website that contains many articles. Two basic
approaches are to either store the articles in aspx files, possibly
indexed by the database, or to store the article text in the database.

Some advantages of storing them in files are simplicity, and efficiency.

Some advantages of storing them in the database are ease of some
operations, and the option of using SQL Server 2005 text index to
implement search.

Can anyone else offer some considerations for choosing between these two
approaches?

Thanks.

Jonathan

Jun 27 '08 #4
Unless you have really simple needs (is this a static site now and for the
foreseeable future ?) I would use a DB. It's likely you'll have anyway to
store other data thna just the description for each article (price,
availability, mark them as deleted, category, user ratings or whatever
else).

--
Patrice

"Jonathan Wood" <jw***@softcircuits.coma écrit dans le message de groupe
de discussion : #L**************@TK2MSFTNGP02.phx.gbl...
I'd like to build a Website that contains many articles. Two basic
approaches are to either store the articles in aspx files, possibly
indexed by the database, or to store the article text in the database.

Some advantages of storing them in files are simplicity, and efficiency.

Some advantages of storing them in the database are ease of some
operations, and the option of using SQL Server 2005 text index to
implement search.

Can anyone else offer some considerations for choosing between these two
approaches?

Thanks.

Jonathan
Jun 27 '08 #5
Can you elaborate on this? The full-text indexing was created for exactly
this purpose. Why does it not do a good job, or is a pain to use?

Thanks.

Jonathan

"George Ter-Saakov" <gt****@cardone.comwrote in message
news:uF**************@TK2MSFTNGP02.phx.gbl...
Implementing search functionality is pain.You might do it yourself or get
some third party solution like dtSearch or open source (just google
"serarch engine open source")

But from my experience the SQL server's full-text do not do a good job.

George.
"Jonathan Wood" <jw***@softcircuits.comwrote in message
news:eL****************@TK2MSFTNGP05.phx.gbl...
>Yeah, these are definitely some of the advantages. Have you made use of
SQL Server 2005's full-text indexing yet? With file-based articles,
implementing search is a pain.

Also, would love to see some samples of the sites you are referring to if
any of them are public.

Jonathan

"Peter Bromberg [C# MVP]" <pb*******@nospammin.yahoo.comwrote in
message news:83**********************************@microsof t.com...
>>We use databases almost exclusively for this kind of "stuff". Its easier
to search, index, etc. and the content can be populated into a
"templatized" article page. It can also be cached via Partial page
caching.
Peter

"Jonathan Wood" <jw***@softcircuits.comwrote in message
news:%2****************@TK2MSFTNGP02.phx.gbl.. .
I'd like to build a Website that contains many articles. Two basic
approaches are to either store the articles in aspx files, possibly
indexed by the database, or to store the article text in the database.

Some advantages of storing them in files are simplicity, and
efficiency.

Some advantages of storing them in the database are ease of some
operations, and the option of using SQL Server 2005 text index to
implement search.

Can anyone else offer some considerations for choosing between these
two approaches?

Thanks.

Jonathan


Jun 27 '08 #6
Yes, I agree that a database will be needed for one purpose or another.

But then how good are my options for implementing search functionality?

Thanks.

Jonathan

"Patrice" <http://www.chez.com/scribe/wrote in message
news:10**********************************@microsof t.com...
Unless you have really simple needs (is this a static site now and for the
foreseeable future ?) I would use a DB. It's likely you'll have anyway to
store other data thna just the description for each article (price,
availability, mark them as deleted, category, user ratings or whatever
else).

--
Patrice

"Jonathan Wood" <jw***@softcircuits.coma écrit dans le message de groupe
de discussion : #L**************@TK2MSFTNGP02.phx.gbl...
>I'd like to build a Website that contains many articles. Two basic
approaches are to either store the articles in aspx files, possibly
indexed by the database, or to store the article text in the database.

Some advantages of storing them in files are simplicity, and efficiency.

Some advantages of storing them in the database are ease of some
operations, and the option of using SQL Server 2005 text index to
implement search.

Can anyone else offer some considerations for choosing between these two
approaches?

Thanks.

Jonathan
Jun 27 '08 #7
Which kind of search ? LIKE would be my first option for text search.
Depends then on how much rows, how much text columns in which to search for
keywords, their size, if you can filter rows using better criteria before
applying LIKE, if users tends to always use the same keywords etc...

Only then you can consider full text search (even SQL Express (with advanced
services) has now full text search)...

--
Patrice

"Jonathan Wood" <jw***@softcircuits.coma écrit dans le message de groupe
de discussion : uf**************@TK2MSFTNGP06.phx.gbl...
Yes, I agree that a database will be needed for one purpose or another.

But then how good are my options for implementing search functionality?

Thanks.

Jonathan

"Patrice" <http://www.chez.com/scribe/wrote in message
news:10**********************************@microsof t.com...
>Unless you have really simple needs (is this a static site now and for
the foreseeable future ?) I would use a DB. It's likely you'll have
anyway to store other data thna just the description for each article
(price, availability, mark them as deleted, category, user ratings or
whatever else).

--
Patrice

"Jonathan Wood" <jw***@softcircuits.coma écrit dans le message de
groupe de discussion : #L**************@TK2MSFTNGP02.phx.gbl...
>>I'd like to build a Website that contains many articles. Two basic
approaches are to either store the articles in aspx files, possibly
indexed by the database, or to store the article text in the database.

Some advantages of storing them in files are simplicity, and efficiency.

Some advantages of storing them in the database are ease of some
operations, and the option of using SQL Server 2005 text index to
implement search.

Can anyone else offer some considerations for choosing between these two
approaches?

Thanks.

Jonathan
Jun 27 '08 #8
In reality it never works well.
I have a web site http://www.mspiercing.com if you look at it you going to
see search box there.

First problem I had is misspells. People on internet do not know how to
spell things. And SQL's full text does not work with misspells.

Another problem was plural vs singular form.

Another problem was weights. If person is looking for "belly ring" I want
the search to find and rank items with word "belly" first simply cause
"ring" exists in pretty much any item.
George.

"Jonathan Wood" <jw***@softcircuits.comwrote in message
news:OI**************@TK2MSFTNGP06.phx.gbl...
Can you elaborate on this? The full-text indexing was created for exactly
this purpose. Why does it not do a good job, or is a pain to use?

Thanks.

Jonathan

"George Ter-Saakov" <gt****@cardone.comwrote in message
news:uF**************@TK2MSFTNGP02.phx.gbl...
>Implementing search functionality is pain.You might do it yourself or get
some third party solution like dtSearch or open source (just google
"serarch engine open source")

But from my experience the SQL server's full-text do not do a good job.

George.
"Jonathan Wood" <jw***@softcircuits.comwrote in message
news:eL****************@TK2MSFTNGP05.phx.gbl...
>>Yeah, these are definitely some of the advantages. Have you made use of
SQL Server 2005's full-text indexing yet? With file-based articles,
implementing search is a pain.

Also, would love to see some samples of the sites you are referring to
if any of them are public.

Jonathan

"Peter Bromberg [C# MVP]" <pb*******@nospammin.yahoo.comwrote in
message news:83**********************************@microsof t.com...
We use databases almost exclusively for this kind of "stuff". Its
easier to search, index, etc. and the content can be populated into a
"templatized" article page. It can also be cached via Partial page
caching.
Peter

"Jonathan Wood" <jw***@softcircuits.comwrote in message
news:%2****************@TK2MSFTNGP02.phx.gbl. ..
I'd like to build a Website that contains many articles. Two basic
approaches are to either store the articles in aspx files, possibly
indexed by the database, or to store the article text in the database.
>
Some advantages of storing them in files are simplicity, and
efficiency.
>
Some advantages of storing them in the database are ease of some
operations, and the option of using SQL Server 2005 text index to
implement search.
>
Can anyone else offer some considerations for choosing between these
two approaches?
>
Thanks.
>
Jonathan
>



Jun 27 '08 #9
Any decent article site MUST have good full-text searching.

--
Jonathan Wood
SoftCircuits Programming
http://www.softcircuits.com

"Patrice" <http://www.chez.com/scribe/wrote in message
news:E7**********************************@microsof t.com...
Which kind of search ? LIKE would be my first option for text search.
Depends then on how much rows, how much text columns in which to search
for keywords, their size, if you can filter rows using better criteria
before applying LIKE, if users tends to always use the same keywords
etc...

Only then you can consider full text search (even SQL Express (with
advanced services) has now full text search)...

--
Patrice

"Jonathan Wood" <jw***@softcircuits.coma écrit dans le message de groupe
de discussion : uf**************@TK2MSFTNGP06.phx.gbl...
>Yes, I agree that a database will be needed for one purpose or another.

But then how good are my options for implementing search functionality?

Thanks.

Jonathan

"Patrice" <http://www.chez.com/scribe/wrote in message
news:10**********************************@microso ft.com...
>>Unless you have really simple needs (is this a static site now and for
the foreseeable future ?) I would use a DB. It's likely you'll have
anyway to store other data thna just the description for each article
(price, availability, mark them as deleted, category, user ratings or
whatever else).

--
Patrice

"Jonathan Wood" <jw***@softcircuits.coma écrit dans le message de
groupe de discussion : #L**************@TK2MSFTNGP02.phx.gbl...
I'd like to build a Website that contains many articles. Two basic
approaches are to either store the articles in aspx files, possibly
indexed by the database, or to store the article text in the database.

Some advantages of storing them in files are simplicity, and
efficiency.

Some advantages of storing them in the database are ease of some
operations, and the option of using SQL Server 2005 text index to
implement search.

Can anyone else offer some considerations for choosing between these
two approaches?

Thanks.

Jonathan

Jun 27 '08 #10
Of those you listed, plural vs singular would be my biggest worry.

Yeah, I understand people don't know how to spell. But if their search
doesn't turn up anything, then I'm not going to feel too guilty when they
misspelled something. Although I understand it's a bit different if your
site is selling stuff, in which case, the site loses when they don't find
what they're looking for.

Thanks.

--
Jonathan Wood
SoftCircuits Programming
http://www.softcircuits.com
"George Ter-Saakov" <gt****@cardone.comwrote in message
news:eJ**************@TK2MSFTNGP05.phx.gbl...
In reality it never works well.
I have a web site http://www.mspiercing.com if you look at it you going to
see search box there.

First problem I had is misspells. People on internet do not know how to
spell things. And SQL's full text does not work with misspells.

Another problem was plural vs singular form.

Another problem was weights. If person is looking for "belly ring" I want
the search to find and rank items with word "belly" first simply cause
"ring" exists in pretty much any item.
George.

"Jonathan Wood" <jw***@softcircuits.comwrote in message
news:OI**************@TK2MSFTNGP06.phx.gbl...
>Can you elaborate on this? The full-text indexing was created for exactly
this purpose. Why does it not do a good job, or is a pain to use?

Thanks.

Jonathan

"George Ter-Saakov" <gt****@cardone.comwrote in message
news:uF**************@TK2MSFTNGP02.phx.gbl...
>>Implementing search functionality is pain.You might do it yourself or
get some third party solution like dtSearch or open source (just google
"serarch engine open source")

But from my experience the SQL server's full-text do not do a good job.

George.
"Jonathan Wood" <jw***@softcircuits.comwrote in message
news:eL****************@TK2MSFTNGP05.phx.gbl.. .
Yeah, these are definitely some of the advantages. Have you made use of
SQL Server 2005's full-text indexing yet? With file-based articles,
implementing search is a pain.

Also, would love to see some samples of the sites you are referring to
if any of them are public.

Jonathan

"Peter Bromberg [C# MVP]" <pb*******@nospammin.yahoo.comwrote in
message news:83**********************************@microsof t.com...
We use databases almost exclusively for this kind of "stuff". Its
easier to search, index, etc. and the content can be populated into a
"templatized" article page. It can also be cached via Partial page
caching.
Peter
>
"Jonathan Wood" <jw***@softcircuits.comwrote in message
news:%2****************@TK2MSFTNGP02.phx.gbl.. .
>I'd like to build a Website that contains many articles. Two basic
>approaches are to either store the articles in aspx files, possibly
>indexed by the database, or to store the article text in the
>database.
>>
>Some advantages of storing them in files are simplicity, and
>efficiency.
>>
>Some advantages of storing them in the database are ease of some
>operations, and the option of using SQL Server 2005 text index to
>implement search.
>>
>Can anyone else offer some considerations for choosing between these
>two approaches?
>>
>Thanks.
>>
>Jonathan
>>
>

Jun 27 '08 #11
George,
You said "I hear all the time how loading a straight file is more
efficient"
And my point was that this is an illusion. That is why many people still
believe it. And you hear it all the time.
File System is designed as a sequential list. If you need to find file
a.txt in it there is no other way but to scan the whole list.
I understand that. My understanding was that transferring the content was
faster from a file that transferring it over a database connection, and not
so much look-up time. My understanding was also that this has been well
testing and documented. But I will certainly admit I haven't ran any tests
myself.
Also MS was planning for long time ago move file system to MS SQL engine.
Not sure if it's still in works or not.
Not sure how great that sounds. Some sort of index to allow a binary lookup
makes sense though.

--
Jonathan Wood
SoftCircuits Programming
http://www.softcircuits.com

Jun 27 '08 #12
So if you are positive you should go for full text search (they are "press
articles" or "products" ?) try for example

http://www.wherecanibuyit.co.uk/ASP/...xt-search.html

--
Patrice

"Jonathan Wood" <jw***@softcircuits.coma écrit dans le message de groupe
de discussion : #f**************@TK2MSFTNGP03.phx.gbl...
Any decent article site MUST have good full-text searching.

--
Jonathan Wood
SoftCircuits Programming
http://www.softcircuits.com

"Patrice" <http://www.chez.com/scribe/wrote in message
news:E7**********************************@microsof t.com...
>Which kind of search ? LIKE would be my first option for text search.
Depends then on how much rows, how much text columns in which to search
for keywords, their size, if you can filter rows using better criteria
before applying LIKE, if users tends to always use the same keywords
etc...

Only then you can consider full text search (even SQL Express (with
advanced services) has now full text search)...

--
Patrice

"Jonathan Wood" <jw***@softcircuits.coma écrit dans le message de
groupe de discussion : uf**************@TK2MSFTNGP06.phx.gbl...
>>Yes, I agree that a database will be needed for one purpose or another.

But then how good are my options for implementing search functionality?

Thanks.

Jonathan

"Patrice" <http://www.chez.com/scribe/wrote in message
news:10**********************************@micros oft.com...
Unless you have really simple needs (is this a static site now and for
the foreseeable future ?) I would use a DB. It's likely you'll have
anyway to store other data thna just the description for each article
(price, availability, mark them as deleted, category, user ratings or
whatever else).

--
Patrice

"Jonathan Wood" <jw***@softcircuits.coma écrit dans le message de
groupe de discussion : #L**************@TK2MSFTNGP02.phx.gbl...
I'd like to build a Website that contains many articles. Two basic
approaches are to either store the articles in aspx files, possibly
indexed by the database, or to store the article text in the database.
>
Some advantages of storing them in files are simplicity, and
efficiency.
>
Some advantages of storing them in the database are ease of some
operations, and the option of using SQL Server 2005 text index to
implement search.
>
Can anyone else offer some considerations for choosing between these
two approaches?
>
Thanks.
>
Jonathan
>

Jun 27 '08 #13
Yes, that's exactly the type of thing I'm considering (I'm already using SQL
Server 2005). But I have seen some complaints about this approach. For
example, loading articles from a database does not appear to be as efficient
as simply displaying files. And I think it was this thread where someone
complained about SQL Server's full indexing's inability to match similar or
plural forms of a word.

Thanks for the link.

--
Jonathan Wood
SoftCircuits Programming
http://www.softcircuits.com

"Patrice" <http://www.chez.com/scribe/wrote in message
news:EC**********************************@microsof t.com...
So if you are positive you should go for full text search (they are "press
articles" or "products" ?) try for example

http://www.wherecanibuyit.co.uk/ASP/...xt-search.html

--
Patrice

"Jonathan Wood" <jw***@softcircuits.coma écrit dans le message de groupe
de discussion : #f**************@TK2MSFTNGP03.phx.gbl...
>Any decent article site MUST have good full-text searching.

--
Jonathan Wood
SoftCircuits Programming
http://www.softcircuits.com

"Patrice" <http://www.chez.com/scribe/wrote in message
news:E7**********************************@microso ft.com...
>>Which kind of search ? LIKE would be my first option for text search.
Depends then on how much rows, how much text columns in which to search
for keywords, their size, if you can filter rows using better criteria
before applying LIKE, if users tends to always use the same keywords
etc...

Only then you can consider full text search (even SQL Express (with
advanced services) has now full text search)...

--
Patrice

"Jonathan Wood" <jw***@softcircuits.coma écrit dans le message de
groupe de discussion : uf**************@TK2MSFTNGP06.phx.gbl...
Yes, I agree that a database will be needed for one purpose or another.

But then how good are my options for implementing search functionality?

Thanks.

Jonathan

"Patrice" <http://www.chez.com/scribe/wrote in message
news:10**********************************@micro soft.com...
Unless you have really simple needs (is this a static site now and for
the foreseeable future ?) I would use a DB. It's likely you'll have
anyway to store other data thna just the description for each article
(price, availability, mark them as deleted, category, user ratings or
whatever else).
>
--
Patrice
>
"Jonathan Wood" <jw***@softcircuits.coma écrit dans le message de
groupe de discussion : #L**************@TK2MSFTNGP02.phx.gbl...
>I'd like to build a Website that contains many articles. Two basic
>approaches are to either store the articles in aspx files, possibly
>indexed by the database, or to store the article text in the
>database.
>>
>Some advantages of storing them in files are simplicity, and
>efficiency.
>>
>Some advantages of storing them in the database are ease of some
>operations, and the option of using SQL Server 2005 text index to
>implement search.
>>
>Can anyone else offer some considerations for choosing between these
>two approaches?
>>
>Thanks.
>>
>Jonathan
>>
>

Jun 27 '08 #14

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

10
by: Dave Moore | last post by:
Hi All, I want to be able to store data as part of my website. I'm assuming that I''ll need to use PHP scripts to provide this functionality, but what would the best aproach be to storing data?. I...
3
by: R Reyes | last post by:
what are the pros/cons of uploading a file into a database (like access, sql server, oracle) vs. uploading a file into a folder (and only storing its path in a database table) ? i've never had...
2
by: Troels Arvin | last post by:
Hello, For some very data-intensive projects it's interesting how much space the DBMS uses for the storage of data, so I'm investigating how space efficient different DBMSes are. In the...
12
by: Jeremy | last post by:
Hi all, I'm getting very confused about how DB2 uses shared memory and I wonder if someone could clarify matters for me, please ? We are running 32bit DB2 V7.2 FP9 under AIX 4.3.3 on a machine...
0
by: Namratha Shah \(Nasha\) | last post by:
Hey Group, After a long week end I am back again. Its nice and refreshing after a short vacation so lets get started with .NET once again. Today we will discuss about Isolated Storage. This is...
4
by: SSUK | last post by:
Hi, Is it better to store files in Database or to store on Hard Disk /network ? On a Web application using .NET...
6
by: cristizaharioiu | last post by:
Hello, I am beginner with db2 ( DB2 v9.1.0.1 running on RHEL 4); this is my first post. I have this error " SQL0968C The file system is full. SQLSTATE=57011"" in my instance configured with...
10
by: Redhairs | last post by:
In a web farm environment, how to store the user uploading files for future access? Store them in db, local file system or centralized file server? If trying to storing the file in local file...
3
by: myjish18 | last post by:
Hello, We have a DB2 UDB database v8.2.7 (db2 v8.2 fixpak 14) on AIX 5.3 which has Automatic Storage (AS) enabled. We want to disable automatic storage on entire database and/or disable...
0
by: DolphinDB | last post by:
Tired of spending countless mintues downsampling your data? Look no further! In this article, you’ll learn how to efficiently downsample 6.48 billion high-frequency records to 61 million...
1
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 6 Mar 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM). In this month's session, we are pleased to welcome back...
0
by: jfyes | last post by:
As a hardware engineer, after seeing that CEIWEI recently released a new tool for Modbus RTU Over TCP/UDP filtering and monitoring, I actively went to its official website to take a look. It turned...
0
by: ArrayDB | last post by:
The error message I've encountered is; ERROR:root:Error generating model response: exception: access violation writing 0x0000000000005140, which seems to be indicative of an access violation...
1
by: Defcon1945 | last post by:
I'm trying to learn Python using Pycharm but import shutil doesn't work
1
by: Shællîpôpï 09 | last post by:
If u are using a keypad phone, how do u turn on JavaScript, to access features like WhatsApp, Facebook, Instagram....
0
by: af34tf | last post by:
Hi Guys, I have a domain whose name is BytesLimited.com, and I want to sell it. Does anyone know about platforms that allow me to list my domain in auction for free. Thank you
0
by: Faith0G | last post by:
I am starting a new it consulting business and it's been a while since I setup a new website. Is wordpress still the best web based software for hosting a 5 page website? The webpages will be...
0
isladogs
by: isladogs | last post by:
The next Access Europe User Group meeting will be on Wednesday 3 Apr 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM). In this session, we are pleased to welcome former...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.