I agree Bryce with most of that except for the comment, "I'm not about to suggest that my 3-employee-client go |out and buy Gentran because they want to sell through Walmart."
Yes, Gentran is over-kill for your scenario, however, there are EDI products that would certainly fit your scenario. We can set up a complete in-house Walmart solution that includes all communication and translation capabilities for all required Walmart documents, including 810 turnaround documents, for a couple of thousand dollars. -Paul ----------------------------------------------------------------- Paul McTeigue President, Icefan Systemhouse Inc. Hudson, Quebec, Canada www.icefan.ca EDI - BBX - Web Development - SQL Server - VB E-Mail: ............. [EMAIL PROTECTED] Voice-Mail: ....... (514) 957-8001 Fax: ................. (450) 458-5625 ----------------------------------------------------------------- |-----Original Message----- |From: [email protected] [mailto:[EMAIL PROTECTED] On |Behalf Of Bryce K. Nielsen |Sent: Monday, January 09, 2006 12:32 PM |To: [email protected] |Subject: Re: [EDI-L] Re: <TECH> Tool for pruning XML Schemas? | | |As an aside, this is partially why Biztalk capped at file |sizes of 20mb in |size. They're translating the file into XML, and a 20mb XML |file will eat up |a good 100mb+ of memory if you're using a DOM parser (which |Biztalk was). | |XML is best used in small, "realtime" messages. In traditional |EDI (read |X12), that is rarely the case which is why XML is usually |shunned by EDI |developers. However, small shops rarely implement |"traditional" EDI. For |example, I'm working with one client who does on average 20 |orders a day. |Their 3 dropship vendors don't want a batch of the orders and |rather want |these orders shot over to them in real-time as an Email. The |message is an |XML attachment that they import directly into their |"backoffice" (which I |think is QuickBooks). None of the parties involved want to |deal with X12, |nor have the budget for an EDI Translator. XML is a perfect |fit for them. | |All technologies have their best-fit scenarios. I'm not about |to suggest |that Walmart should use XML because it's the latest fad. But |at the same |time, I'm not about to suggest that my 3-employee-client go |out and buy |Gentran because they want to sell through Walmart. | |Bryce K. Nielsen |SysOnyx, Inc. (www.sysonyx.com) |Tutorial on xmlLinguist, the EDI-to-XML Translator: |http://www.sysonyx.com/xml-to-edi-850 | | |----- Original Message ----- |From: "john r" <[EMAIL PROTECTED]> |To: "Jim Divoky" <[EMAIL PROTECTED]>; <[email protected]> |Sent: Sunday, January 08, 2006 10:21 AM |Subject: Re: [EDI-L] Re: <TECH> Tool for pruning XML Schemas? | | |> The "simple" difference(I'm sure someone can give a more technical |> reason) in speed that you would see from a SAX to a DOM has |to do with |> file size. A SAX parser will read element to next node and |pass upon |> validation releasing the memory after it has valedated. A |DOM will try |> and load the entire data file as an object attempting to |valedate the |> entire file in one pass. So if you have a 100K file the DOM would |> probably easily and speedily handle the message. If you get |to say 1M |> file the DOM has to allocate a lot of memory so its |performance suffers. |> The thing about parsing is that if validation is turned on |you ALWAYS end |> up getting 2-3 times minimum the amount of data you are |loading in memory |> or you end up with 3-5 times the amount of data on disc. |Small files |> never really hurt you(unless you load alot). Big files can |kill you with |> DOM though. |> |> just a thought, |> | | | |. |Please use the following Message Identifiers as your subject |prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> |Access the list online at: http://groups.yahoo.com/group/EDI-L | |Yahoo! Groups Links | | | | | | . Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Access the list online at: http://groups.yahoo.com/group/EDI-L Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
