Date
1 - 4 of 4
Making Web-enabled
|
Hi,
I am still working in V9.4SP8 with Btrieve database. I want to make my applications web-enabled. It is about 260Mb of Magic control files and about 30 years of development. I also use GET.DLL and some ownbuild OCX/DLL components. I want to do it right the first time, so I am thinking of three possibilities to do this: 1. Migrate to XPA and use RIA and how will RIA handle components I they are rebuild in DOTNET 2. Use Magic Broker and develope the webside by a thirty party tool 3. Leave Magic and develope by a thirty party tool May be there are more options, may be there are company's offering conversion to web-enabled. As I think these considerations has passed a lot of you, please can you share your experiances? Best regards, André |
|
|
|
Craig Martin
Magic broker is solid and just works. HTML-merge serves all. Gigaspaces helps to you scale to Google/Netflix orders of magnitude but unlikely you need it.
Lots of choices for javascript frameworks. React wins.
Just an opinion.
Craig From: main@magicu-l.groups.io <main@magicu-l.groups.io> on behalf of De Netwerkadviseur BV <andre@...>
Sent: Thursday, August 17, 2017 12:34:45 AM To: main@magicu-l.groups.io Subject: [magicu-l] Making Web-enabled Hi,
I am still working in V9.4SP8 with Btrieve database. I want to make my applications web-enabled. It is about 260Mb of Magic control files and about 30 years of development. I also use GET.DLL and some ownbuild OCX/DLL components. I want to do it right the first time, so I am thinking of three possibilities to do this: 1. Migrate to XPA and use RIA and how will RIA handle components I they are rebuild in DOTNET 2. Use Magic Broker and develope the webside by a thirty party tool 3. Leave Magic and develope by a thirty party tool May be there are more options, may be there are company's offering conversion to web-enabled. As I think these considerations has passed a lot of you, please can you share your experiances? Best regards, André |
|
|
|
Tim Downie
unless you try and post a % in your xml body :( then it all breaks.
From: main@magicu-l.groups.io <main@magicu-l.groups.io> on behalf of Craig Martin <craig@...>
Sent: Thursday, 24 August 2017 5:30 AM To: main@magicu-l.groups.io Subject: Re: [magicu-l] Making Web-enabled Magic broker is solid and just works. HTML-merge serves all. Gigaspaces helps to you scale to Google/Netflix orders of magnitude but unlikely you need it.
Lots of choices for javascript frameworks. React wins.
Just an opinion.
Craig From: main@magicu-l.groups.io <main@magicu-l.groups.io> on behalf of De Netwerkadviseur BV <andre@...>
Sent: Thursday, August 17, 2017 12:34:45 AM To: main@magicu-l.groups.io Subject: [magicu-l] Making Web-enabled Hi,
I am still working in V9.4SP8 with Btrieve database. I want to make my applications web-enabled. It is about 260Mb of Magic control files and about 30 years of development. I also use GET.DLL and some ownbuild OCX/DLL components. I want to do it right the first time, so I am thinking of three possibilities to do this: 1. Migrate to XPA and use RIA and how will RIA handle components I they are rebuild in DOTNET 2. Use Magic Broker and develope the webside by a thirty party tool 3. Leave Magic and develope by a thirty party tool May be there are more options, may be there are company's offering conversion to web-enabled. As I think these considerations has passed a lot of you, please can you share your experiances? Best regards, André |
|
|
|
Hi Craig,
Thank you for your opinion. I am already testing the magic broker and it look likes to be the best option. Best regards, André |
|
|