Re: FrontBase

2017-03-27 Thread William Luu 
You might have more luck on their dev mailing list?
http://www.frontbase.com/cgi-bin/WebObjects/FBWebSite

I did a Google search on the error message (Wrong magic number) in your
stackexchange post and found these:
- https://lists.apple.com/archives/webobjects-dev/2010/Sep/msg00706.html
- https://lists.apple.com/archives/webobjects-dev/2010/Sep/msg00698.html


Which is are the only results I could find with that error message and
frontbase.

Did a bit more searching around importing backup to another platform, which
yielded the below:

"Can I export a database with WRITE ALL OUTPUT and then import it on
another platform?
Yes. When you perform a WRITE ALL OUTPUT you will be exporting into a flat
file that can be subsequently imported on any supported platform"

via
http://www.frontbase.com/cgi-bin/WebObjects/FBWebSite.woa/1/wa/supportPage?currentPage=Faqs=2






On 24 March 2017 at 21:42, Craig van Nieuwkerk  wrote:

> The biggest issue I have so far is I can't restore the database. See my
> question here
>
> http://dba.stackexchange.com/questions/167306/restoring-a-
> frontbase-database
>
>
> On Fri, Mar 24, 2017 at 9:37 PM, Preet Sangha 
> wrote:
>
>> Never used it myself - but looking through the docs I think i supports
>> ODBC, to perhaps you can use a tools like MS Query/Access etc to access it?
>>
>>
>> regards,
>> Preet, in Auckland NZ
>>
>>
>> On 24 March 2017 at 23:14, Craig van Nieuwkerk  wrote:
>>
>>> I have a backup of a FrontBase (http://www.frontbase.com) database that
>>> I am trying to access. Does anyone have any experience with this? I have
>>> tried using the tools from their website to restore but to no avail.
>>>
>>> Thanks
>>> Craig
>>>
>>
>>
>

RE: WebApi - PUT and DELETE

2017-03-27 Thread djones147 
Hi all, 

Many years ago I had to debug a problem with a web server that used Delete to 
remove files on the server. The reason it failed was that a proxy server was 
rejecting the PUT and DELETE verbs.

Fast forward to six months ago,  I was argued out of only using POST and GET on 
the service call, we implemented PUT, DELETE, POST and GET. 

One week ago, I find out that there is a bug raised where PUT is being refused 
from a client from a remote location and they can’t figure out why. 

As far as I am concerned PUT and DELETE were only ever part of the original 
RFC. They were never implemented correctly and should be treated with upmost 
distain when they are used. 

.02c
Davy


Sent from Mail for Windows 10

From: Tony Wright
Sent: 27 March 2017 05:43
To: ozDotNet
Subject: Re: WebApi - PUT and DELETE

Well, we're well into development and have delivered a bunch of apps already, 
and it hasn't done anything to us so far. As long as we stick with the "use GET 
to retrieve data" and "use POST to modify data" basic rules, then I don't think 
we can come unstuck. In fact, this has to be acceptable because, if you read 
the pages and pages and pages and pages of arguments, you'll find some 
statements about PUT and DELETE being marked as obsolete anyway in some 
environments, and plenty of people using POST and GET only. REST has really 
stolen the http protocol and has used it for an originally unintended purpose. 
I'm kind of getting a bit sick of developments' collective claim that one path 
is best practice and another isn't, with no statistical analysis/mathematical 
proof that one way is, in fact, better than another.

On Mon, Mar 27, 2017 at 2:32 PM, Greg Keogh  wrote:
I think we'll stick with the RPC style of call and not go with a RESTful 
interface, and anyone that cares that much about it in an interview can go and 
get a pointier hat.

Oooh, I'd still try to do things the restful way and follow the "standards" 
(cough, ahem!), or "conventions". If you want to do it the RPC way then you 
should probably use a SOAP service with real contracts. You might run into 
libraries that expect you to follow the "conventions", I dunno for sure, but 
I'd play it safe -- GK